Buildbot: Difference between revisions
Jump to navigation
Jump to search
(link release automation docs) |
ChrisCooper (talk | contribs) |
||
| Line 9: | Line 9: | ||
* [http://mxr.mozilla.org/seamonkey/source/tools/buildbot-configs/testing/unittest/ Unit Test CVS (mxr)] | * [http://mxr.mozilla.org/seamonkey/source/tools/buildbot-configs/testing/unittest/ Unit Test CVS (mxr)] | ||
* [[BuildbotTestfarm|Test Farm Setup]] | |||
* [[BuildbotTestFarmUse|Test Farm User's Manual]] | |||
* Reference Platforms | * Reference Platforms | ||
** [[ReferencePlatforms/Test/WinXP (Tinderbox)|WinXP (Tinderbox)]] | ** [[ReferencePlatforms/Test/WinXP (Tinderbox)|WinXP (Tinderbox)]] | ||
** [[ReferencePlatforms/Test/Linux FC4 (Tinderbox)|Linux FC4 (Tinderbox)]] | ** [[ReferencePlatforms/Test/Linux FC4 (Tinderbox)|Linux FC4 (Tinderbox)]] | ||
** [[ReferencePlatforms/Test/Linux FC6 (Tinderbox)|Linux FC6 (Tinderbox)]] | ** [[ReferencePlatforms/Test/Linux FC6 (Tinderbox)|Linux FC6 (Tinderbox)]] | ||
* [[Buildbot/OutageReports| Outage Reports]] | * [[Buildbot/OutageReports| Outage Reports]] | ||
= Talos (Performance Testing) = | = Talos (Performance Testing) = | ||
Revision as of 12:03, 2 September 2007
Buildbot is being used at Mozilla today in a number of different ways. This page will serve as the clearinghouse for finding Buildbot-related information. Please try to keep it organized as you add to it.
Unit Testing
- Unit Test CVS (mxr)
- Test Farm Setup
- Test Farm User's Manual
- Reference Platforms
- Outage Reports
Talos (Performance Testing)
- General Info
- Talos CVS (mxr)
- Buildbot Installation, Operation, Development, Issues
- Reference Platforms
- Outage Reports
Build/Release Automation
- Release Automation docs
- Reference Platforms
"Try" Server
Mozilla2
Axel's Original Buildbot Requirements
A collection of random things that buildbot should do. Please add your item, what it's supposed to do, and an owner, if applicable.
- running python on the slave
- (Axel) Sample impl should be reviewable soon. Major trick is to add an import of your module to the buildbot start script to hook up the registerSlaveCommand
- ensure directory on slave
- (Axel) Using the code above
- single source checkout per slave
- (Axel) This required a blocking scheduler to make all builds run on one source version per slave, together with a lock per slave that notifies the waiting build steps, in this case, to not check out. For multiple check-out targets, this requires the ....
- BuildStepGroup
- (Axel, help-wanted) This groups a set of steps together, so that they don't loose the lock. I have a somewhat working implementation, but I think that the status reporting is wonky.
- Download nightly builds on slave
- (nobody) For l10n repackaging, we need to find out when new nightly builds are available, which source time stamp they have, and get them into the right location on the slave.
- Compare locales
- (Axel) They python implementation can now run natively in the slave, and report a dict object back for rich log parsing on the master, or in a web-facing post processing.