Merge lp:~cjwatson/charms/trusty/turnipcake/build-label into lp:~canonical-launchpad-branches/charms/trusty/turnipcake/devel
Status: | Merged |
---|---|
Merged at revision: | 22 |
Proposed branch: | lp:~cjwatson/charms/trusty/turnipcake/build-label |
Merge into: | lp:~canonical-launchpad-branches/charms/trusty/turnipcake/devel |
Diff against target: |
449 lines (+220/-82) 6 files modified
.bzrignore (+1/-2) Makefile.common (+24/-21) config.yaml (+28/-0) deploy-requirements.txt (+0/-1) hooks/actions.py (+165/-55) hooks/services.py (+2/-3) |
To merge this branch: | bzr merge lp:~cjwatson/charms/trusty/turnipcake/build-label |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+275469@code.launchpad.net |
Commit message
Allow updating the code payload separately from the charm using a build label.
Description of the change
Allow updating the code payload separately from the charm using a build label. This parallels https:/
The approach used here is based heavily on the software-
The virtualenv moves inside the payload directory so that each payload gets its own. /srv/turnipcake
There are no tests directly here, but it'll at least get integration testing by way of the corresponding changes to the Mojo spec.
Approving as a parallel of https:/ /code.launchpad .net/~cjwatson/ charms/ trusty/ turnip/ build-label/ +merge/ 275468.