All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Autobuilder upgrade to Buildbot 0.8.3
Date: Thu, 23 Dec 2010 21:28:32 -0800	[thread overview]
Message-ID: <4D142F80.3090308@intel.com> (raw)
In-Reply-To: <DC74E0187B44084E9AD28300B75DFE300557D6E7@orsmsx504.amr.corp.intel.com>

On 12/23/2010 11:45 AM, Flanagan, Elizabeth wrote:
> All,
>
> I've now finished the upgrade of the autobuilder repo to include buildbot 0.8.3. I've rewritten the installer and updated a bunch of build helper files. I wanted to take a few moments to explain some of the changes regarding installation.
>
> The big change is the upgrade to buildbot 0.8.3. Buildbot now keeps the master and slave code in different tarballs, so I've split up the installer to allow people to install either a master, a slave or both.
>
> I've also added some command line args to help people in configuration of a local BB. To see the long form of usage:
>
> git clone git://git.pokylinux.org/poky-autobuilder
> cd poky-autobuilder
> ./scripts/poky-setup-autobuilder --help
>
> The quickest way to set up the autobuilder for developer use, is to do:
>
> ./scripts/poky-setup-autobuilder both
> cd ~/poky-master
> make start
> cd ~/poky-slave
> make start
> open a browser to http://localhost:8010
>
Ok, so what is the User and Password for?  I don't really see any 
explanation for them.

I am trying different options for setting locations and seem to have run 
into trouble.  It would be nice to have a general option to just sent 
bbHome to something other than home directory to move everything to a 
different drive.

Sau!


> If for some reason the bb uses too many cpu cycles, you *should* be able to do:
>
> nice -n 20 make start
>
> I haven't tested this though so YMMV.
>
> This creates a minimal pokyABConfig.py within ~/poky-master. There is a longer more complex pokyABConfig.py within scripts called pokyABConfig.py.example but for most developers, the default should suffice. If you need to turn off some buildsets in pokyABConfig.py, just edit it and comment out the build steps you don't need and issue a
>
> make reconfig
>
> If something went funny (ie you don't see your changes) tail out the twistd.log file for debug info.
>
> I've tested this on opensuse and ubuntu, but would appreciate any feedback, especially for folks doing more complicated installs (multiple slave builders, etc)
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2010-12-24  5:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23 19:45 Autobuilder upgrade to Buildbot 0.8.3 Flanagan, Elizabeth
2010-12-24  5:28 ` Saul Wold [this message]
2010-12-26 17:36   ` Flanagan, Elizabeth
2010-12-26 22:07     ` Saul Wold
2010-12-27 10:12 ` Mei, Lei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D142F80.3090308@intel.com \
    --to=saul.wold@intel.com \
    --cc=elizabeth.flanagan@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.