canmove, Confirmed users
6,439
edits
ReleaseEngineering/Buildbot Best Practices: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Buildbot Best Practices (view source)
Revision as of 14:13, 20 March 2009
, 20 March 2009→Check-in Policies
No edit summary |
|||
| Line 14: | Line 14: | ||
* If you have a patch that affects multiple masters you should update all of the masters when you land your patch. | * If you have a patch that affects multiple masters you should update all of the masters when you land your patch. | ||
** This is less strict for staging masters. Eg, you shouldn't update a staging master if someone is currently using it. | ** This is less strict for staging masters. Eg, you shouldn't update a staging master if someone is currently using it. | ||
* There are no staging repositories for buildbot or buildbotcustom. Because of this you should never check in code to either of these repositories until it is properly reviewed and about to be deployed in production. | |||
** If you want to keep these repositories version controlled while doing development/testing you should create a user repository for them. | |||
== How to land a patch == | == How to land a patch == | ||