User:Rhelmer:Migrating Tinderbox to Buildbot: Difference between revisions

User:Rhelmer:Migrating Tinderbox to Buildbot (view source)

834 bytes added , 15 February 2008

give some reasons why

canmove, Confirmed users

1,511

edits

@@ Line 1: / Line 1: @@
+=Why?=
+* [http://buildbot.net Buildbot] is supported by a vibrant, active community. Nobody uses Tinderbox client but Mozilla, as far as I know
+* Buildbot gives developers more direct control and insight over the currently running builds with features such as stopping/starting builds from the web interface and real-time log output.
+* The Buildbot codebase is subjectively cleaner; development is certainly more active, and has very good code coverage via unit tests
+* Buildbot lets us use machines more effectively by building in parallel and only building when a checkin happens. This reduces cycle time, uses less overall resources, and gives us a build for each and every changeset. Contrast with our current method of standalone machines which build as often as possible, regardless of whether there's been a change or not.
+=Shorter term=
 It's probably fastest and safest to keep Tinderbox server in place, with Buildbot reporting to it, at least until we get the [[User:Rhelmer:Buildbot/Tinderbox server parity|Buildbot/Tinderbox server parity]] issues figured out.
-=Shorter term=
 ==Use existing release automation==
 On the client side, we have been working on automating the release process using [http://mxr.mozilla.org/mozilla/source/tools/release/ Bootstrap] driven by Buildbot; making this system work for Nightly(Clobber) and Depend builds should be fairly trivial.