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 18:29, 12 November 2007
, 12 November 2007synopsis
m (clarify where client.mk is used) |
(synopsis) |
||
| Line 1: | Line 1: | ||
=Shorter term= | ==Shorter term - Use existing release automation== | ||
Short-term it's probably | Short-term it's probably fastest and safest to keep Tinderbox server in place, with Buildbot reporting to it, until we get the [[User:Rhelmer:Buildbot/Tinderbox server parity|Buildbot/Tinderbox server parity]] issues figured out. | ||
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. | 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. | ||
| Line 27: | Line 27: | ||
We need #1 and #2 done for release automation anyway, #3 and #4 are trivial. | We need #1 and #2 done for release automation anyway, #3 and #4 are trivial. | ||
=Longer Term= | ==Longer Term - Call build system from Buildbot== | ||
Long-term we can have Buildbot drive the process at a lower level. | Long-term we can have Buildbot drive the process at a lower level. | ||