Closed Bug 643471 Opened 14 years ago Closed 9 years ago

need a place to set defaults for release configs

Categories

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

Product:
Release Engineering
Component:
Release Automation: Other
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

Details

(Whiteboard: [configs])

There's a lot of duplication across release configs which is annoying, and sometimes causes issues when we need to mass-update them -- it's very easy to screw it up. We should have a place to set branch defaults as well as production/staging/preproduction defaults for release configs. This is very similar to what's already done for regular dep/nightly configs, but I don't think release-specific variables should be intertwined there. Also, we have no use for platform defaults in releases. A couple ideas: - Set up separate data structures in the existing {production,staging,preproduction}_config.py and config.py for release variables. - Define defaults in data structures at the top of process/release.py
Ben: still needed?
Component: Release Engineering → Release Engineering: Automation
OS: Linux → All
Priority: P4 → --
QA Contact: release → catlee
Hardware: x86_64 → All
Whiteboard: [configs]
I still think it would useful, yeah.
Severity: normal → enhancement
Priority: -- → P3
Bulk move of bugs to Release Automation component.
Component: Release Engineering: Automation (General) → Release Engineering: Automation (Release Automation)
Mass move of bugs to Release Automation component.
No longer blocks: hg-automation
Product: mozilla.org → Release Engineering
This may end up being wontfix/unnecessary with CI build promotion.
Release configs are dead after the upcoming release promotion work is done, this isn't worth fixing now.
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.