Merge lp:~bloodearnest/juju-deployer/annotate-branches into lp:juju-deployer
| Status: | Approved |
|---|---|
| Approved by: | Kapil Thangavelu on 2015-07-02 |
| Approved revision: | 130 |
| Proposed branch: | lp:~bloodearnest/juju-deployer/annotate-branches |
| Merge into: | lp:juju-deployer |
| Diff against target: |
100 lines (+38/-2) (has conflicts) 5 files modified
deployer/action/importer.py (+12/-0) deployer/tests/test_data/wiki-branch.yaml (+5/-0) deployer/tests/test_data/wiki.yaml (+1/-1) deployer/tests/test_guiserver.py (+1/-1) deployer/tests/test_importer.py (+19/-0) Text conflict in deployer/action/importer.py |
| To merge this branch: | bzr merge lp:~bloodearnest/juju-deployer/annotate-branches |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Kapil Thangavelu | 2014-10-22 | Approve on 2015-07-02 | |
|
Review via email:
|
|||
Commit Message
Annotate a service with the branch information on deploy.
Description of the Change
Annotate a service with the branch information on deploy.
This lays the ground work for being able to produce upgrade charms in diff.
| Kapil Thangavelu (hazmat) wrote : | # |
| Kapil Thangavelu (hazmat) wrote : | # |
this branch also setups a test with a nonsensical config by specifying a branch for a store charm.
| Simon Davy (bloodearnest) wrote : | # |
On Tue, Feb 3, 2015 at 12:09 PM, Kapil Thangavelu
<email address hidden> wrote:
> so a minor on this would be to actually record the vcs revision in the annotation with charm.get_
good idea, will do.
| Simon Davy (bloodearnest) wrote : | # |
On Tue, Feb 3, 2015 at 12:57 PM, Kapil Thangavelu
<email address hidden> wrote:
> this branch also setups a test with a nonsensical config by specifying a branch for a store charm.
Right, I will copy the test-wiki fixture and change to non-cs charm.
| Simon Davy (bloodearnest) wrote : | # |
Hi Kapil
Have addressed review comments, let me know if there's anything else.
The only thing I would like to be able to do is annotate branch/revision when deploying directly from the store, perhaps we can use the store api to get the bzr revision that a particular store revision matches up to, i dunno.
| Kapil Thangavelu (hazmat) wrote : | # |
The branch seems to be referencing a test data file that is not in the branch
- 131. By Simon Davy on 2015-07-16
-
add missing test data file
- 132. By Simon Davy on 2015-07-16
-
fix local repo clean up
| Simon Davy (bloodearnest) wrote : | # |
I've added the file that was missing, and fixed test clean up issue, should be good to go
Unmerged revisions
- 132. By Simon Davy on 2015-07-16
-
fix local repo clean up
- 131. By Simon Davy on 2015-07-16
-
add missing test data file
- 130. By Simon Davy on 2015-03-30
-
merge upstream and fix review comments
- 129. By Simon Davy on 2014-10-22
-
whitespace clean up
- 128. By Simon Davy on 2014-10-22
-
whitespace clean up
- 127. By Simon Davy on 2014-10-22
-
add branch annotations on deploy

so a minor on this would be to actually record the vcs revision in the annotation with charm.get_ vcs().get_ cur_rev( ) added to the annotation.