release_sanity.py should check for tuples where there shouldn't be any

RESOLVED WORKSFORME

Status

P5
normal
RESOLVED WORKSFORME
7 years ago
2 years ago

People

(Reporter: aki, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [releases][automation])

I think this is heavy handed, but in 9.0b1 I set the l10n relbranch to 'None,' which makes it a tuple.

This resulted in the tagging step looping for a long time trying and failing to tag the l10n repos.
maybe a simple schema that describes which keys are required, optional, and what types they should be?
(Reporter)

Comment 2

7 years ago
Sounds similar to bug 699343 :)
No longer blocks: 714371
Mass move of bugs to Release Automation component.
Blocks: 714371
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: 714371
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
No more release configs! \o/
Status: NEW → RESOLVED
Last Resolved: 2 years ago
QA Contact: rail
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.