Re: svn trunk r21152: FAIL (i686-debian-sarge1 shared gcc-3.3.5)
From: Paul Burba <paulb_at_softlanding.com>
Date: 2006-08-23 12:59:00 CEST
--------------------------------------------------------------------- To unsubscribe, e-mail: email@example.com For additional commands, e-mail: firstname.lastname@example.org Received on Wed Aug 23 12:59:46 2006
-----Lieven Govaerts <email@example.com> wrote: -----
>Concerning your remark about how you're using (or not using)
>assume you're used to a continuous integration solution, where a
>build leads to lava lamps glowing red, public humiliation or buying
>croissants (er donuts?) for the whole team.
>The Subversion buildbot is setup with a broader purpose:
>First of all it's about continuous integration obviously: fast
>on build problems so people don't waste time fixing a broken build.
>Expected resolution time: asap.
>Second, we run all the regression tests (currently ra_local only) on
>new revision, thereby testing if that change doesn't change the
>svn in a negative way. Expected resolution time: a few days max.
>Third, buildbot slaves are installed on multiple platforms. For now
>these are Debian Sarge, Windows XP & Mac , but I hope to expand that.
>give developers access to other platforms to use at work/home. If a
>platform specific issue shows up during a build step, we can't blame
>change committer for that.
>So, don't hesitate to let buildbot test your patch.
Thanks for the info. I was largely ignorant of all things regarding the buildbot setup.
>In fact, the reason why buildbot was chosen, was because it has a
>feature to try a patch first on one or more slaves before committing.
>you try a patch, buildbot will update to the last revision, apply
>patch, build and test it but it won't send an email to the
>list (you can check the result on the webpage).
This would definitely be helpful in situations like the debian failure, since in this case I knew that there was a platform specific failure lurking in my patch.
>Currently I'm the only one using the try mechanism, but if you or
>committers are interested I can explain you how it works. Or, I can
>present buildbot and the try feature on the Summit.
A presentation would be very helpful.
This is an archived mail posted to the Subversion Dev mailing list.