canmove, Confirmed users
2,850
edits
CIDuty/Reconfigs: Difference between revisions
no edit summary
No edit summary |
ChrisCooper (talk | contribs) No edit summary |
||
| Line 10: | Line 10: | ||
* executing a buildbot reconfig command on each buildbot master | * executing a buildbot reconfig command on each buildbot master | ||
Please see the [ | Please see the [[ReleaseEngineering/How_To/Land_Buildbot_Master_Changes|instructions for how to land buildbot changes]] for more information. | ||
It is polite to ask in #releng if anyone has further changes to land before starting the reconfig process. | It is polite to ask in #releng if anyone has further changes to land before starting the reconfig process. | ||
| Line 43: | Line 43: | ||
= Updating the pinned version of mozharness on mozilla-central = | = Updating the pinned version of mozharness on mozilla-central = | ||
{{Release Engineering How To|Update the pinned version of mozharness}} | {{Release Engineering How To|Update the pinned version of mozharness|Update the pinned version of mozharness}} | ||
The revision of [https://hg.mozilla.org/build/mozharness mozharness] used by a particular branch of mozilla code is now tracked in-tree. As a courtesy to developers and sheriffs, buildduty is expected to update the pinned revision in the mozilla-central integration branch when they move the <code>production</code> tag. The change will be merged from mozilla-central to other branches by sheriffs as part of their normal duties. | The revision of [https://hg.mozilla.org/build/mozharness mozharness] used by a particular branch of mozilla code is now tracked in-tree. As a courtesy to developers and sheriffs, buildduty is expected to update the pinned revision in the mozilla-central integration branch when they move the <code>production</code> tag. The change will be merged from mozilla-central to other branches by sheriffs as part of their normal duties. | ||
| Line 69: | Line 69: | ||
In general, linux test masters are the slowest to reconfig. You can tail the manage_masters-##########.log to keep up with progress. By default, this log is created in /tmp/reconfig. | In general, linux test masters are the slowest to reconfig. You can tail the manage_masters-##########.log to keep up with progress. By default, this log is created in /tmp/reconfig. | ||
If the reconfig gets stuck, see [ | If the reconfig gets stuck, see [[ReleaseEngineering/How_To/Unstick_a_Stuck_Slave_From_A_Master|How To/Unstick a Stuck Slave From A Master]]. | ||