lp://staging/~frankban/charms/precise/juju-gui/bug-1100194-add-charm-options
- Get this branch:
- bzr branch lp://staging/~frankban/charms/precise/juju-gui/bug-1100194-add-charm-options
Branch merges
- Juju GUI Hackers: Pending requested
-
Diff: 249 lines (+103/-17)7 files modifiedconfig.yaml (+22/-0)
config/config.js.template (+3/-0)
hooks/config-changed (+9/-5)
hooks/start (+3/-2)
hooks/utils.py (+24/-6)
revision (+1/-1)
tests/test_utils.py (+41/-3)
Related bugs
Bug #1100194: Add username, password and read-only options to the charm | Medium | Fix Released |
Related blueprints
Branch information
- Owner:
- Francesco Banconi
- Status:
- Development
Recent revisions
- 25. By Francesco Banconi
-
Juju GUI source as env var + Charm test branch
This branch introduces the possibility to provide
the Juju GUI source (used in tests) by setting an
environment variable. This way the charm tests can
be run as part of the release qa process, e.g.:$ JUJU_GUI_SOURCE=lp:mybranch jitsu test juju-gui ...
or, to test a new trunk release:
$ JUJU_GUI_
SOURCE= trunk jitsu test juju-gui ... Also updated the test exercising the process of
making a release from a branch, i.e. when the
juju-gui-source option points to a Bazaar branch.Now the branch used is a customized one, present in
`lp:~frankban/juju-gui/charm-tests-branch` (please
feel free to suggest another, more sane, location,
and please take a look at that as part of your reviews).
This is a test branch containing only a minimal
Makefile and a release tarball. There, `make distfile`
is almost a no-op, and for this reason the charm test
speed is slightly increased (~4 minutes on ec2).
Source: http://bazaar. launchpad. net/~frankban/ juju-gui/ charm-tests- branch/ files R=gary.poster, teknico
CC=
https://codereview. appspot. com/7102044
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)