Closed Bug 1286562 Opened 8 years ago Closed 10 months ago

don't delete MARs that are used in watershed or other long lived updates

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

Details

Rail and I discovered that the current watershed for SHA-1 on nightly and aurora is broken because we delete the MARs that those Balrog blobs point at after 1 month. We're going to need a way to keep MARs like this for indefinite periods of time to make sure this doesn't happen in the future.

Bonus points for automatically retaining anything currently pointed at by a Balrog blob, but that might be quite a stretch.
Component: General Automation → General

Something changed at some point (I have no idea when or where), and we no longer delete nightly MARs AFAICT.

Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED

We delete partials after a while, but maybe that's fine because we'll fall back to a complete mar instead and those stick around?

Flags: needinfo?(bhearsum)

(In reply to Julien Cristau [:jcristau] from comment #2)

We delete partials after a while, but maybe that's fine because we'll fall back to a complete mar instead and those stick around?

Thanks - I (obviously) didn't catch that part. Falling back to the complete should be fine.

Flags: needinfo?(bhearsum)
You need to log in before you can comment on or make changes to this bug.