need a place to set defaults for release configs

RESOLVED WONTFIX

Status

Release Engineering
Release Automation
P3
enhancement
RESOLVED WONTFIX
7 years ago
2 years ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [configs])

(Reporter)

Description

7 years ago
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
No longer blocks: 627271
Blocks: 714371

Comment 1

6 years ago
Ben: still needed?
Component: Release Engineering → Release Engineering: Automation
OS: Linux → All
Priority: P4 → --
QA Contact: release → catlee
Hardware: x86_64 → All
Whiteboard: [configs]
(Reporter)

Comment 2

6 years ago
I still think it would useful, yeah.

Updated

6 years ago
Severity: normal → enhancement
Priority: -- → P3
(Reporter)

Comment 3

6 years ago
Bulk move of bugs to Release Automation component.
Component: Release Engineering: Automation (General) → Release Engineering: Automation (Release Automation)
(Reporter)

Comment 4

6 years ago
Mass move of bugs to Release Automation component.
(Reporter)

Updated

6 years ago
No longer blocks: 714371
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
(Reporter)

Comment 5

3 years ago
This may end up being wontfix/unnecessary with CI build promotion.
(Reporter)

Comment 6

2 years ago
Release configs are dead after the upcoming release promotion work is done, this isn't worth fixing now.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.