Closed
Bug 1100474
Opened 10 years ago
Closed 10 years ago
Do not lock aurora updates by default
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: rail)
References
Details
Attachments
(1 file)
|
681 bytes,
patch
|
bhearsum
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
The current merge process requires to run it in 2 passes: 1) migrate 2) manually verify 1) and push (or fix the issues and rerun 1) again) Removing lock-update-paths from default actions and calling it explicitly in 2) should resolve the issue.
Attachment #8524005 -
Flags: review?(bhearsum)
|
||
Comment 1•10 years ago
|
||
Comment on attachment 8524005 [details] [diff] [review] mozharness-no-lock-update-paths.diff Agreed! Thanks for fixing this.
Attachment #8524005 -
Flags: review?(bhearsum) → review+
|
Assignee | |
Comment 2•10 years ago
|
||
Comment on attachment 8524005 [details] [diff] [review] mozharness-no-lock-update-paths.diff https://hg.mozilla.org/build/mozharness/rev/412fc8f62e17
Attachment #8524005 -
Flags: checked-in+
|
|
Assignee | |
Comment 3•10 years ago
|
||
https://wiki.mozilla.org/index.php?title=ReleaseEngineering%2FMerge_Duty%2FSteps&diff=1034126&oldid=1033228
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
Comment 4•10 years ago
|
||
Comment on attachment 8524005 [details] [diff] [review] mozharness-no-lock-update-paths.diff in production
|
||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•