we need a way to mark a build record as superseded
Bug #419318 reported by
LaMont Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Currently, marking an infinitely retrying build requires SQL hackery to mark the build record superseded. This should be converted to a script that the OSAs can run.
thanks,
lamont
| Changed in soyuz: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: soyuz-core |
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| tags: | added: canonical-losa-lp |
To post a comment you must log in.
If canceling a build record is a legitimate request (not only an sporadic action to mitigate other problems) I think we should not overload the meaning of BuildStatus.
From what I've seen, the use-case is:
Buildd administrators (possibly uploaders too) need a way to *cancel* a build record. The cancellation might be reversible in same cases, via the 'Retry' action.
Agreeing on that, we should extend BuildStatus with CANCELED item and implement 'Cancel this build' action in the UI (and the API).
(Note that tracking users responsible for build status change is already an systematic problem on Build, e.g. who retried a build ? or how many times it was retried ? This aspect should be considered)