On Wed, Jul 23, 2008 at 6:50 AM, Iago Toral Quiroga <
itoral igalia com> wrote:
El mar, 22-07-2008 a las 11:40 +0100, John Carr escribió:
> I have pushed what I have so far to
bzr-playground.gnome.org:
>
> bzr branch
>
http://bzr-playground.gnome.org/~johncarr/jhbuildbot/trunk
>
> You should be able to browse the history there too. Some of
> this is more hardcoded that it should be, but you should be
> able to get a feel for the new approach that the buildbot
> people suggested. This branch is very close to solving the
> following two goals:
>
> * Upgrade to 0.7.7
> * Only use 2 ports (right now: 9070 for build slaves, 8080
> for http)
Be careful! I've been testing with a patch to only have 1 or 2 projects loaded, if you try it with all projects it will probably try and build and once. Moving over the serial scheduler stuff is my task for on the train this morning :-)
> When its a bit more mature it should also:
>
> * Make deploying slaves easy (via jhbuild)
>
> Before that though I need to:
>
> * Make sure builds run in the right order (migrate Serial
> scheduler to the new system)
> * Make sure that build-on-commit works
Mmm... does this mean that you want to build a module whenever there is
a commit to it? That's too much imho.
At the moment i'm only trying to make sure all the code that already exists is ported over. There is a GNOME CVS Mail change source shipped with jhbuild-buildbot-scripts.
I agree building on commit is probably too much, but at the same time I want to see the state of my project more than once every 6 hours. I'm not a fan of building *everything* on a timer even if there is not a change. So perhaps (when the initial work is done) we can exploit some of the more advanced schedulers in buildbot to build more frequently (hourly, half hourly), but only if there is a change etc.
> * Port over the skinning stuff
> * Port over the home page (where we had a summary)
Basics of this are done now.
Iago
