canmove, Confirmed users
1,511
edits
User:Rhelmer:Migrating Tinderbox to Buildbot: Difference between revisions
User:Rhelmer:Migrating Tinderbox to Buildbot (view source)
Revision as of 02:34, 15 February 2008
, 15 February 2008better way to contrast quality
(code quality jab) |
(better way to contrast quality) |
||
| Line 1: | Line 1: | ||
=Why?= | =Why?= | ||
* [http://buildbot.net Buildbot] is supported by a vibrant, active community, and is used by [http://buildbot.net/trac/wiki/SuccessStories lots of other projects]. | * [http://buildbot.net Buildbot] is supported by a vibrant, active community, and is used by [http://buildbot.net/trac/wiki/SuccessStories lots of other projects]. | ||
* Buildbot itself goes through a continuous integration process, and requires unit tests for code changes. | |||
* 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. | * 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. | ||
* 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. | * 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. | ||