Closed Bug 1038673 Opened 11 years ago Closed 9 years ago

Add a consistency check on the ship-it build

Categories

(Release Engineering :: Applications: Shipit, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Sylvestre, Assigned: Sylvestre)

Details

(Whiteboard: [shipit])

Attachments

(2 files)

Yesterday, I made the mistake to build fennec beta 10 from the release branch. The patch adds a check to display a warning in this case (and could be extended to add further checks).
Attachment #8456122 - Flags: review?(rail)
Attached image Example of the result
This seems like the sort of thing that release sanity should be checking, not Ship It. When bug 847424 is fixed, this (and all the other errors that release sanity can detect) will be raised to Ship It's interface.
I am not sure I agree here. We, release managers, want to have this feedback in the ship-it interface in order to fix the potential mistake before the build starts.
(In reply to Sylvestre Ledru [:sylvestre] from comment #3) > I am not sure I agree here. We, release managers, want to have this feedback > in the ship-it interface in order to fix the potential mistake before the > build starts. This is what release sanity is for - which runs prior to the release starting, and halts the entire process if there's an error (it resets the "ready" flag in ship it, too). It's unfortunate that it doesn't expose its entire output on Ship It, but this is exactly the type of thing that release sanity is for.
Comment on attachment 8456122 [details] [diff] [review] 0001-Display-a-warning-when-a-beta-build-is-started-from-.patch Sylvestre and I talked about this on Vidyo. He's going to look at adding this as an additional check to release sanity (https://github.com/mozilla/build-tools/blob/master/buildbot-helpers/release_sanity.py). bug 847424 is tracking exposing failures from release sanity on ship it - which will make them more visible to everyone.
Attachment #8456122 - Flags: review?(rail) → review-
Assignee: nobody → sledru
I agree that this should be part of the existing release sanity checks. I think there is also a point to be made to have these checks in the UI at the time when we're creating a new release. The earlier we identify potential issues the cheaper it is to fix them.
Mass component change for ship it bugs.
Component: Release Automation → Ship It
With what we have currently in ship-it, we don't need to implement that now.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: