CIDuty/Reconfigs: Difference between revisions

Jump to navigation Jump to search
Line 42: Line 42:
The script will also attempt to update IRC with reconfig status. To do so, it uses a minimal bash IRC client called [http://tools.suckless.org/ii/ ii]. You can [http://tools.suckless.org/ii/ download ii from their website], or install it via a package manager (e.g. port install ii). Updating irc is non-fatal, but make sure ''ii'' is in your PATH if you want it to work.
The script will also attempt to update IRC with reconfig status. To do so, it uses a minimal bash IRC client called [http://tools.suckless.org/ii/ ii]. You can [http://tools.suckless.org/ii/ download ii from their website], or install it via a package manager (e.g. port install ii). Updating irc is non-fatal, but make sure ''ii'' is in your PATH if you want it to work.


= Updating the pinned version of mozharness on mozilla-inbound =
= 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}}
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-inbound integration branch when they move the <code>production</code> tag. The change will be merged from mozilla-inbound 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.


The pinned revision is tracked in this file: https://hg.mozilla.org/integration/mozilla-inbound/file/7431168bfa3b/testing/mozharness/mozharness.json
The pinned revision is tracked in this file: http://hg.mozilla.org/mozilla-central/file/920ded6a1f77/testing/mozharness/mozharness.json


Update the revision in the file to point to the revision of the new mozharness <code>production</code> tag and land normally.
Update the revision in the file to point to the revision of the new mozharness <code>production</code> tag and land normally.
Confirmed users
1,989

edits

Navigation menu