Closed
Bug 819088
Opened 12 years ago
Closed 8 years ago
release sanity should check if previous releases set in the web form are final
Categories
(Release Engineering :: Applications: Shipit, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Unassigned)
Details
(Whiteboard: [shipit])
We hit this with ESR 17.0.1 when prev build was set to build1 instead of build2. We can checkout tagged release configs and load them to check those.
|
Reporter | |
Updated•12 years ago
|
Priority: -- → P2
|
||
Updated•12 years ago
|
Whiteboard: [kickoff] → [shipit]
|
|
Reporter | |
Updated•12 years ago
|
Assignee: rail → nobody
Priority: P2 → --
|
|
||
Updated•12 years ago
|
Priority: -- → P3
|
Assignee | |
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
|
|
||
Comment 1•10 years ago
|
||
Mass component change for ship it bugs.
Component: Release Automation → Ship It
|
|
Reporter | |
Comment 2•8 years ago
|
||
This is fixed now. We compare buildN to the actually released files.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•3 years ago
|
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in
before you can comment on or make changes to this bug.
Description
•