Closed Bug 855291 Opened 12 years ago Closed 8 years ago

ship it should handle reconfig/sendchange failures differently than release sanity ones

Categories

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

Product:
Release Engineering
Component:
Applications: Shipit
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

Details

(Whiteboard: [shipit])

Currently, whenever we hit any sort of error in release runner we mark all of the releases that we were processed as failed. This works great for release sanity issues because we haven't committed any changes yet, so someone can edit the problematic releases on the ship it website and try again. However, after the release config bumps have been pushed the release should no longer be editable. In fact, editing it after that is likely to cause a problem. I'm not sure exactly what we'd want to do here....we definitely want _something_ to show up on the ship it dashboard. And we probably want to mark it as not ready, because it's unlikely that we want to retry over and over again without intervention. bug 847424 might make this easier.
Product: mozilla.org → Release Engineering
Mass component change for ship it bugs.
Component: Release Automation → Ship It
No more reconfigs!
Status: NEW → RESOLVED
Closed: 8 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.