Add juju-ci-tools

mthaddon · May 16, 2017 · fcd484d · fcd484d
2 parents a3d86e2 + d370579
commit fcd484d
Show file tree

Hide file tree

Showing 500 changed files with 71,579 additions and 0 deletions.
diff --git a/acceptancetests/.bzrignore b/acceptancetests/.bzrignore
@@ -0,0 +1,11 @@
+./manual-provider-home
+./juju-ci-tools.common_*.deb
+/.idea
+/logs
+/repository
+./.coverage
+__pycache__
+./jujupy.egg-info
+./dist
+./jujupy-*
+./build
diff --git a/acceptancetests/COPYING b/acceptancetests/COPYING
diff --git a/acceptancetests/COPYING.LESSER b/acceptancetests/COPYING.LESSER
@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
diff --git a/acceptancetests/Makefile b/acceptancetests/Makefile
@@ -0,0 +1,32 @@
+p=test*.py
+py3="assess_model_change_watcher.py"
+test:
+	TMPDIR=/tmp python -m unittest discover -vv . -p "$(p)"
+	TMPDIR=/tmp python3 -m unittest discover -vv jujupy -t . -p "$(p)"
+lint:
+	python3 -m flake8 --builtins xrange,basestring $(py3)
+	flake8 $$(find -name '*.py') --builtins xrange,basestring --exclude $(py3)
+cover:
+	python -m coverage run --source="./" --omit "./tests/*" -m unittest discover -vv ./tests
+	python -m coverage report
+clean:
+	find . -name '*.pyc' -delete
+
+apt-update:
+	sudo apt-get -qq update
+juju-ci-tools.common_0.1.4-0_all.deb: apt-update
+	find . -name '*.deb' -delete
+	sudo apt-get install -y equivs
+	equivs-build juju-ci-tools-common
+install-deps: juju-ci-tools.common_0.1.4-0_all.deb apt-update
+	sudo dpkg -i juju-ci-tools.common_0.1.4-0_all.deb || true
+	sudo apt-get install -y -f
+	./pipdeps.py -v install
+name=NAMEHERE
+assess_file=assess_$(name).py
+test_assess_file=tests/test_assess_$(name).py
+new-assess:
+	install -m 755 template_assess.py.tmpl $(assess_file)
+	install -m 644 template_test.py.tmpl $(test_assess_file)
+	sed -i -e "s/TEMPLATE/$(name)/g" $(assess_file) $(test_assess_file)
+.PHONY: lint test cover clean new-assess apt-update install-deps
diff --git a/acceptancetests/README.md b/acceptancetests/README.md
@@ -0,0 +1,63 @@
+# Continuous Integration scripts
+
+The Juju QA team uses a common set or tests that exercise the release tools
+and juju to verify that each revision of juju can be released, built, packaged,
+published, installed, bootstrapped, and deployed.
+
+CI requires
+    lp:juju-release-tools (The packaging and publication tools)
+    lp:juju-ci-tools (This branch)
+    lp:juju-ci-tools/repository (A copy of the juju charm repository)
+    And a JUJU_HOME with all the envs to test.
+
+The general process involves making a release tarball, making a package,
+making a tree of tools and metadata, and lastly publishing the tools.
+you can skip the tarball and package steps if you just want to publish
+the juju tools (AKA jujud, servers, agents). If you want to test a fix
+that is in the juju-core trunk branch, you can make your own release
+tarball and package.
+
+Once juju is published to the test clouds, individual tests can be performed.
+Most tests accept an env name. The envs define the cloud and series to test.
+
+## Requirements for running tests
+You will need some python libraries in order to run the existing CI tests.
+Install the following
+
+sudo apt-get install python-launchpadlib python-yaml python-boto python-mock
+ python-jenkins python-novaclient python-pexpect python-winrm python-coverage
+
+In addition, if you wish to use azure, you will need to install pip, and the
+associated client library from pip for azure.
+
+sudo apt-get install python-pip
+pip install azure
+
+# Creating a New CI Test
+
+Test scripts will be run under many conditions to reproduce real cases.
+Most scripts cannot assume special knowledge of the substrate, region,
+bootstrap constraints, tear down, and log collection, etc.
+
+If this is your first time, consider asking one of the QA team to pair-program
+on it with you.
+
+You can base your new script and its unit tests on the template files.
+They provide the infrastructure to setup and tear down a test. Your script
+can focus on the unique aspects of your test. Start by making a copy of
+template_assess.py.tmpl, and don't forget unit tests!
+
+    make new-assess name=my_function
+
+Run make lint early and often. (You may need to do sudo apt-get install python-
+flake8). If you forget, you can run autopep8 to fix certain issues. Please use
+--ignore E24,E226,E123 with autopep8. Code that's been hand-written to follow
+PEP8 is generally more readable than code which has been automatically
+reformatted after the fact. By running make lint often, you'll absorb the style
+and write nice PEP8-compliant code.
+
+Please avoid creating diffs longer than 400 lines. If you are writing a new
+test, that may mean creating it as a series of branches. You may find bzr-
+pipeline to be a useful tool for managing a series of branches.
+
+If your tests require new charms, please write them in Python.