Launchpad fails to trigger new snap builds on git changes
Bug #1786832 reported by
Stéphane Graber
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Colin Watson | ||
Bug Description
I've recently noticed that the LXD snap didn't get a new build triggered even 50min after a new commit got pushed to Launchpad.
https:/
https:/
Colin tracked this down to OOPS-7e151a22c4191874801f2de4105d5a79 which shows another git branch where a snapcraft.yaml can't be found and is preventing any other snap (after that error is reached) from getting triggered.
For now I'll just keep triggering builds manually but this likely affects quite a few other snaps.
Related branches
lp:~cjwatson/launchpad/snap-auto-builds-oops
- William Grant: Approve (code)
-
Diff: 103 lines (+59/-22)2 files modifiedlib/lp/snappy/model/snap.py (+29/-22)
lib/lp/snappy/tests/test_snap.py (+30/-0)
| tags: | added: fallout lp-snappy oops regression trivial |
| Changed in launchpad: | |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| assignee: | nobody → Colin Watson (cjwatson) |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r18751 <http://