OCI build fails all push rules after the first failure
Bug #1888578 reported by
Thiago F. Pappacena
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Thiago F. Pappacena | ||
Bug Description
When an OCI build finishes and there are several push rules for that recipe, if one of the push rules fails Launchpad is not trying to upload using the next push rules.
We came across this a few times, and it's not the expected behavior. If one of the push rules fails to upload, we should try the next push rule.
Related branches
~pappacena/launchpad:continue-oci-push-on-failure
- Colin Watson (community): Approve
-
Diff: 281 lines (+138/-55)3 files modifiedlib/lp/oci/interfaces/ociregistryclient.py (+14/-0)
lib/lp/oci/model/ociregistryclient.py (+64/-49)
lib/lp/oci/tests/test_ociregistryclient.py (+60/-6)
| Changed in launchpad: | |
| assignee: | nobody → Thiago F. Pappacena (pappacena) |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| tags: | added: buildfarm oci |
| Changed in launchpad: | |
| status: | New → Triaged |
| Changed in launchpad: | |
| status: | Triaged → Fix Committed |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
