canmove, Confirmed users
1,511
edits
No edit summary |
(longer term buildbot ideas) |
||
| Line 1: | Line 1: | ||
=Shorter term= | |||
Short-term it's probably best 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. | Short-term it's probably best 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. | ||
| Line 26: | 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= | |||
Long-term we can have Buildbot drive the process at a lower level. | |||
The process should be something like: | |||
7 builders total: | |||
* Source (checks out using timestamp, creates tarball) | |||
* (Linux/Mac/Windows)-(Clobber/Depend) | |||
Clobber builds are triggered by the nightly scheduler (or manually) and do the following: | |||
# Source builder creates and uploads source tarball | |||
# (Linux/Mac/Windows)-Clobber builders | |||
## download source, unpack | |||
## configure | |||
## make package | |||
## build crashreporter | |||
## create full MAR | |||
## upload package, symbols, MAR | |||
Depend builds are triggered by checkins (e.g. using BonsaiPoller) (or manually) and do the following; | |||
# (Linux/Mac/Windows)-Depend builders | |||
## update existing source checkout | |||
## configure | |||
## make package | |||
## upload package | |||