Confirmed users
283
edits
ReleaseEngineering/Buildbot Best Practices: Difference between revisions
ReleaseEngineering/Buildbot Best Practices (view source)
Revision as of 15:46, 25 August 2009
, 25 August 2009→Check-in Policies: Update obsolete link
No edit summary |
(→Check-in Policies: Update obsolete link) |
||
| Line 8: | Line 8: | ||
== Check-in Policies == | == Check-in Policies == | ||
* '''Patches should not be landed during code freeze periods''' | * '''Patches should not be landed during code freeze periods''' | ||
* We track configuration updates to our masters on [[ReleaseEngineering: | * We track configuration updates to our masters on [[ReleaseEngineering:Maintenance | Maintenance]]. Any change to a production Buildbot Master should be tracked on this page. | ||
* Patches should not be checked in until you are ready to update the master with them. This helps to avoid situations where an urgent fix needs to go in, and a random unrelated patch ends up getting enabled at the same time. | * Patches should not be checked in until you are ready to update the master with them. This helps to avoid situations where an urgent fix needs to go in, and a random unrelated patch ends up getting enabled at the same time. | ||
* All affected masters running production instances must be updated. | * All affected masters running production instances must be updated. | ||