Closed Bug 1303908 Opened 4 years ago Closed 2 years ago

graph2 script should verify build number

Categories

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

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rail, Unassigned)

References

Details

(Whiteboard: [releaseduty])

Instead of pushing Firefox 49.0 build4 to the releases directory we copied build1. We should probably verify that the build number is the latest build and make it harder to submit graph2 otherwise.

We can probably check the build number against the latest index entry.
See Also: → 1303909
Planning to work on this at the beginning of Q4. Feel free to reassign if there's someone else volunteering for it in the meantime.
Assignee: nobody → mtabara
Priority: -- → P2
Found in triaging. Good first bug for releaseduty improving release automation.
Keywords: good-first-bug
Whiteboard: [releaseduty]
Assignee: mtabara → nobody
Priority: P2 → P3
We should make sure this is fixed in rr3.
Removing good-first-bug because system is going away soon, but not quite dead yet.
Keywords: good-first-bug

Given that we no longer copy-paste commands and have them instead in Ship-it all around in production, I think we can close this. Please re-open should I'm missing anything.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.