Closed Bug 1444159 Opened 7 years ago Closed 6 years ago

set in-tree release graphs to 5 days deadline

Categories

(Release Engineering :: Release Automation: Other, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mtabara, Unassigned)

References

Details

(Whiteboard: [releaseduty])

In the old releasetasks graphs we used to have 5 days expiration policy for the graphs. We're having a much better model now with the snowman, where each phase is supposed to run in less than 24h, and theoretically we shouldn't need this expiration bump (which by the way, most likely got lost when we migrated things over from releasetasks). However, there are cases like we have the promotion phase for XX.0Yb1 on Friday (first week after mergeduty) and then we discover next Monday issues with the tasks and we need reruns. There's always workaround to copy-paste + edit the task and rerun but rerunning might be handier. Non-urgent though.
s,expiration,deadline,
(In reply to Aki Sasaki [:aki] from comment #1) > s,expiration,deadline, Doh, mea culpa. Expiration is set to never for release artifacts. I'm amending this to avoid confusion. Thanks for pointing this out.
Summary: set in-tree release graphs to 5 days expiration → set in-tree release graphs to 5 days deadline
Priority: -- → P1
Second thoughts on this, decreasing priority, not that important for now.
Priority: P1 → P2
Graphs already have this deadline set for 1 day, I think we can close this.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.