Closed Bug 1219714 Opened 9 years ago Closed 9 years ago

Release sanity should check if ship-it revision comes after merge commit

Categories

(Release Engineering :: Release Automation, defect)

Product:
Release Engineering
Component:
Release Automation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: rail, Unassigned)

References

Details

In bug 1219581 we hit a situation where the changeset entered to ship-it was on a branch not descendant of the merge changeset. We ended up building beta code instead of release code.
I experienced a similar issue with 45. When building from mozilla-release, we should do a stupid "grep official mobile/android/config/mozconfigs/android-api-11/release" to check that it is correct.
Assignee: nobody → mtabara
Not currently working on this, deferring to avoid blocking.
Assignee: mtabara → nobody
See Also: → 1282959
We explicitly check this by checking version_display.txt, which would fail in this case (it contains "b").
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.