Closed
Bug 607570
Opened 15 years ago
Closed 9 years ago
ReleaseUpdatesFactory fails if the update verify config file has already been bumped
Categories
(Release Engineering :: Release Automation, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Unassigned)
Details
(Whiteboard: [release-process-improvement][automation][updates])
commit_verify_configs fails on second run:
hg commit -m Automated configuration bump: update verify configs for 3.6.12 build 1
...
nothing changed
program finished with exit code 1
Should be very similar to bug 466999.
|
||
Comment 1•15 years ago
|
||
Is this bug specific to major update? If not, I'm not sure how it's different to bug 466999
|
||
Comment 2•15 years ago
|
||
I see that this is for the update verify configs and bug 466999 is for the patcher config file, does that change whether or not this is a dupe?
|
||
Updated•15 years ago
|
Priority: -- → P3
Whiteboard: [release-process-improvement][automation][updates]
|
Assignee | |
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
|
|
||
Comment 3•11 years ago
|
||
Is this still an issue?
|
|
Reporter | |
Comment 4•11 years ago
|
||
I think so. ReleaseUpdatesFactory.bumpConfigs() runs "hg commit", and if one tries to run the same builder again (if uploadSnippets() fails for some reason), it will fail.
As a possible work around we can run "hg push" just before we call self.trigger()
|
|
||
Updated•11 years ago
|
Component: Other → Release Automation
QA Contact: bhearsum
|
|
Reporter | |
Comment 5•9 years ago
|
||
This is fixed in release promotion.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•