lp:~frankban/charms/precise/juju-gui/charmworld-fix

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~juju-gui/charms/precise/juju-gui/trunk at revision 66

charmers: Pending requested 2013-06-11

Diff: 0 lines api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

67. By Francesco Banconi on 2013-06-11

Bumped up revision.

66. By Francesco Banconi on 2013-06-11

Fix charmworld url.

65. By Francesco Banconi on 2013-06-10

Replace jitsu test with juju-test.

This branch makes juju-test the default test runner
for both the unit tests and the charm functional tests.

The charm test suite now supports both pyJuju and juju-core.

The tests dependencies are now installed in a virtualenv that
is automatically created and updated by the first test
executable (00-setup). This way we don't require the user
to install all the packages, and, moreover, we make the tests
ready to be run in the charm testing infrastructure.

When the charm is deployed during tests, a temporary repository
is created where the charm is copied and then deployed.
This way we achieve two important goals:
- the developer is not forced to manually set up a local
Juju repository where to branch the Juju GUI;
- the charm can be deployed even if it contains a virtualenv, i.e.
a directory with absolute symlinks (that's because the .venv dir
is not copied in the temp repo).

The tests/helpers.py and tests/deploy.py files will be eventually
replaced by similar tools provided by the juju testing harness.

Updated the documentation where required.

Fixed unit tests exit code.

Common commands (test/lint/clean etc.) can now be easily run
using make.

Nice to have, not included in this branch:
  - collect deployment test logs;
  - reintroduce a way to test the charm specifying a
    different juju-gui-source;
  - do not require the branch to be named "juju-gui".

PS: sorry for the diff, well over 1k loc :-/

R=
CC=
https://codereview.appspot.com/9874050

64. By Nicola Larosa on 2013-06-06

Fix backend unit tests.

Make the backend unit tests not expect any extra repositories.

R=frankban, bac
CC=
https://codereview.appspot.com/10020044

63. By Brad Crittenden on 2013-06-04

[TRIVIAL] Add .lbox for specifying the target

R=
CC=
https://codereview.appspot.com/10009043

62. By Brad Crittenden on 2013-06-04

Fix the discrepancy between dev and rel branches.

Changes that should've been submitted to the development branch of the gui
(lp:~juju-gui/charms/precise/juju-gui/trunk) were instead merged into the
release branch (lp:charms/juju-gui).

This branch merges those changes back into devel for on-going work. The
premature release will remain in place.

R=teknico
CC=
https://codereview.appspot.com/9975046

61. By Francesco Banconi on 2013-06-03

Take the juju API address from the environment

The charm now tries to retrieve the juju API
address from the hook context before parsing
the machiner agent file.

This way we take advantage of a change in juju-core
currently in review, which introduces the corresponding
functionality.

R=
CC=
https://codereview.appspot.com/9810044

60. By Nicola Larosa on 2013-05-23

Describe how to use juju-core in README.md .

Update README.md with instructions specific to juju-core, with regard
to the alternative for the update-to pyjuju command.

R=bac
CC=
https://codereview.appspot.com/9676045

59. By Nicola Larosa on 2013-05-22

Allow "juju-origin: lp:juju" in env.

Fix charm to work when juju-origin is set to lp:juju in the environment.
QAed with both lp:juju and ppa as values.

R=jeff.pihach, bac
CC=
https://codereview.appspot.com/9646043

58. By Francesco Banconi on 2013-05-17

Support juju-gui-source=branch:revno

Added support for creating and deploying
a release from a specific branch revision.

R=bac, jeff.pihach
CC=
https://codereview.appspot.com/9464043