Confirmed users
67
edits
CIDuty/Reconfigs: Difference between revisions
Jump to navigation
Jump to search
m
Update BuildDuty to CiDuty. Renaming project
m (Jlund moved page ReleaseEngineering/Buildduty/Reconfigs to Buildduty/Reconfigs: Buildduty has moved beyond the scope of Release Engineering and now lends support to additional Firefox CI related teams) |
m (Update BuildDuty to CiDuty. Renaming project) |
||
| Line 2: | Line 2: | ||
{{Release Engineering How To|Reconfigs}} | {{Release Engineering How To|Reconfigs}} | ||
A reconfig (short for "reconfigure the buildbot masters") is how changes to buildbot configurations make it into production. | A reconfig (short for "reconfigure the buildbot masters") is how changes to buildbot configurations make it into production. CiDuty is responsible for running reconfigs. | ||
In a nutshell, a reconfig consists of: | In a nutshell, a reconfig consists of: | ||
| Line 47: | Line 47: | ||
= Updating the pinned version of mozharness on mozilla-central = | = Updating the pinned version of mozharness on mozilla-central = | ||
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, | 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, CiDuty 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 pinned revision is tracked in this file: http://hg.mozilla.org/mozilla-central/file/920ded6a1f77/testing/mozharness/mozharness.json | The pinned revision is tracked in this file: http://hg.mozilla.org/mozilla-central/file/920ded6a1f77/testing/mozharness/mozharness.json | ||