Merge lp://qastaging/~bac/juju-quickstart/qa-procedure into lp://qastaging/juju-quickstart
Proposed by
Brad Crittenden
Status: | Merged |
---|---|
Merged at revision: | 77 |
Proposed branch: | lp://qastaging/~bac/juju-quickstart/qa-procedure |
Merge into: | lp://qastaging/juju-quickstart |
Diff against target: |
104 lines (+54/-9) 1 file modified
HACKING.rst (+54/-9) |
To merge this branch: | bzr merge lp://qastaging/~bac/juju-quickstart/qa-procedure |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju GUI Hackers | Pending | ||
Review via email: mp+222704@code.qastaging.launchpad.net |
Description of the change
Add QA procedures to HACKING.rst
New QA steps added. Also updated PPA build procedure given we have bifurcated
the pre-trusty and trusty-and-beyond steps.
To post a comment you must log in.
Reviewers: mp+222704_ code.launchpad. net,
Message:
Please take a look.
Description:
Add QA procedures to HACKING.rst
New QA steps added. Also updated PPA build procedure given we have
bifurcated
the pre-trusty and trusty-and-beyond steps.
https:/ /code.launchpad .net/~bac/ juju-quickstart /qa-procedure/ +merge/ 222704
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/103290043/
Affected files (+56, -9 lines):
M HACKING.rst
A [revision details]
Index: HACKING.rst
=== modified file 'HACKING.rst'
--- HACKING.rst 2014-02-19 13:27:04 +0000
+++ HACKING.rst 2014-06-10 17:37:55 +0000
@@ -73,14 +73,57 @@
$ .venv/bin/python juju-quickstart --help
+Pre-release QA quickstart- beta gui/quickstart- beta mediawiki mediawiki mediawiki/ single ~~~~~~~ ~~~~~~~ ~~
+~~~~~~~~~~~~~~
+
+The general steps for manual QA (until we get a continuous integration set
up
+with functional tests) should be run on trusty and saucy.
+
+* Ensure juju-quickstart is installed from the juju-gui/
PPA.::
+
+ sudo add-apt-repository ppa:juju-
+ sudo apt update
+ sudo apt install juju-quickstart
+
+* Remove juju from the system.::
+
+ sudo apt-get remove --purge juju-core
+
+* Verify LXC environments can boot from scratch, using a local bundle::
+
+ mkdir $HOME/bundles
+ bzr branch lp:~charmers/charms/bundles/mediawiki/bundle
$HOME/bundles/
+ juju-quickstart -e local -n single $HOME/bundles/
+ juju destroy-environment local -y
+
+* Verify an environment that has already been bootstrapped is recogized and
+ the GUI is deployed::
+
+ juju bootstrap -e local
+ juju quickstart -e local bundle:
+ juju destroy-environment local -y
+
+Repeat above on ec2.
+
Creating PPA releases
~~~~~
+Due to an inconsistency of package names for the websocket package
introduced
+with trusty, the juju-quickstart packaging must be handled separately for
+series before trusty and trusty and later. Consequently, there are two
+packaging branches and two build recipes. The two packaging branches are:
+
+* lp:~juju-gui/juju-quickstart/packaging-trunk, and
+* lp:~juju-gui/juju-quickstart/packaging-pre-trusty
+
+For the following instructions we'll use the -trunk version but the
procedure
+is the same for the -pre-trusty branch.
+
The packaging repository (including the ``debian`` directory) can be
checked
-out from lp:~juju-gui/juju-quickstart/packaging/, e.g.::
+out from lp:~juju-gui/juju-quickstart/packaging-trunk, e.g.::
- $ bzr branch lp:~juju-gui/juju-quickstart/packaging/ packaging
- $ cd packaging
+ $ bzr branch lp:~juju-gui/juju-quickstart/packaging-trunk/
packaging-trunk
+ $ cd packaging-trunk
Check that the packaging version reflects the latest Quickstart version. changelog` ` file present in
The
packaging version can be found in the ``debian/
the
@@ -99,7 +142,7 @@
to the packaging branch trunk, and follow the instructions below.
The recipe for creating packages is in /code.launchpad .net/~juju- gui-charmers/ +recipe/ juju-quickstart -daily>. /code.launchpad .net/~juju- gui-charmers/ +recipe/ juju-quickstart -trunk- daily>.
-<https:/
+<https:/
We currently publish beta release...