Closed bac closed 8 years ago
Note this change is related to the issue https://github.com/CanonicalLtd/charmstore-client/issues/155
Test PASSed. Refer to this link for build results (access rights to CI server needed): http://ci.jujugui.org:8080//job/juju-gui-charm/5/ Test PASSed.
Update looks :+1:; trying QA now.
QA:
Using the provided bundle I ran quickstart; everything came up and the bundle deployed fine.
I was also able to deploy a mix of other charms.
QA OK.
:shipit:
Status: merge request accepted. Url: http://ci.jujugui.org:8080/job/juju-gui-charm-merge
See https://bugs.launchpad.net/juju-quickstart/+bug/1532005
QA:
You can publish a version of this charm to your namespace and then use it with juju quickstart to ensure that it works. The following bundle has a charm that is only published to the new charmstore so it is a good test. Quickstart should deploy both charms.
It can be invoked like:
You should also deploy this charm and ensure you can deploy charms that have been ingested and those that are only published directly to the new charmstore.