Closed Bug 813072 Opened 10 years ago Closed 6 years ago

Push to mirrors doesn't happen with disabled updates

Categories

(Release Engineering :: Release Automation: Other, defect, P3)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Unassigned)

Details

... because push to mirrors is in post-updates builder list.

This happens for first releases of ESR builds. I'm OK with wontfixing this if the logic becomes obscure.
I think we just need to remove 'releaseConfig.get('verifyConfigs'):' from the conidition: https://github.com/mozilla/buildbotcustom/blob/master/process/release.py#L1695

I'm not sure why that condition was there in the first place. It was added in bug 708656.
even if you remove that condition that builder remains in post_updates which won't be triggered:
https://github.com/mozilla/buildbotcustom/blob/master/process/release.py#L1711
Priority: -- → P3
Product: mozilla.org → Release Engineering
Still an issue in 24.0 esr. Easy work around is to force the push_to_mirrors builder.
This is not the case in release promotion
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.