Add option to trigger snap builds when top-level branch changes

Bug #1593359 reported by Colin Watson on 2016-06-16
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Colin Watson

Bug Description

We'd like to have an option to automatically trigger snap builds when the top-level branch changes. Evan asked for this in connection with the Jenkins snap, but it's come up before as well. At the moment the best we can offer is that people can automate this externally using the API, which isn't nothing, but it's a wart if we want to be able to give upstream developers something very easy to manage.

The reason I didn't include auto-build support initially was that it was prohibitively difficult to tell when any of the components that go into a snap have changed, and this is still true. But we probably shouldn't let the perfect be the enemy of the good here; we can always extend it later.

Related branches

Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Colin Watson (cjwatson) wrote :

2016-06-20 20:12:00,578 INFO 2209-69-4 applied just now in 0.3 seconds

tags: added: qa-ok
removed: qa-needstesting
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Launchpad QA Bot (lpqabot) wrote :
Launchpad QA Bot (lpqabot) wrote :
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
status: In Progress → Fix Committed
Colin Watson (cjwatson) on 2016-07-14
tags: added: qa-ok
removed: qa-needstesting
Colin Watson (cjwatson) on 2016-07-15
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers