Closed Bug 1181724 Opened 9 years ago Closed 9 years ago

esr31 should get a copy of mozharness that matches its current pin

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jlund, Unassigned)

References

Details

another special snowflake that won't be getting many (any?) uplifts before the end of the month so we don't need to worry about merging mozharness diffs from newer release branches. But if we do have a chemspill, it would be nice to know for sure that esr31 will build+test like it does currently
esr31 already has a copy of mozharness that is at rev: 4d855a6835ed

via:
https://hg.mozilla.org/releases/mozilla-esr31/rev/7105dab57de8
https://hg.mozilla.org/releases/mozilla-esr31/rev/e6a1ef7a16fa

this will need to be backed out and a new mozharness copy pushed in that matches: https://hg.mozilla.org/releases/mozilla-esr31/file/036b844a4d01/testing/mozharness/mozharness.json
esr31 is dyyyyyyyying
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.