Adding Vagrantfile for local developer testing
This Vagrantfile attempts to replicate the gate check testing to the extent possible to allow developers to run all tests locally in a Vagrant environment prior to submitting changes for review. Contributor documentation updated to demonstrate usage of the Vagrantfile. Change-Id: Iaf6cd27730521db648338cb297f8282b1eb71d05
This commit is contained in:
parent
7e759bc93b
commit
8ac7e261d8
|
@ -60,3 +60,6 @@ releasenotes/build
|
||||||
|
|
||||||
# Test temp files
|
# Test temp files
|
||||||
tests/plugins
|
tests/plugins
|
||||||
|
|
||||||
|
# Vagrant testing artifacts
|
||||||
|
.vagrant
|
||||||
|
|
|
@ -28,11 +28,29 @@ the workflow documented at: "http://docs.openstack.org/infra/manual/developers.h
|
||||||
|
|
||||||
Pull requests submitted through GitHub will be ignored and closed without regard.
|
Pull requests submitted through GitHub will be ignored and closed without regard.
|
||||||
|
|
||||||
|
If you wish to test your changes locally prior to submitting them for review
|
||||||
|
you can use the ``Vagrantfile`` included in the root of this repository. It
|
||||||
|
aims to replicate the gate check testing that will be done by OpenStack CI
|
||||||
|
once your review has been submitted.
|
||||||
|
|
||||||
|
To run tests:
|
||||||
|
|
||||||
|
.. code-block:: shell-session
|
||||||
|
|
||||||
|
# vagrant up
|
||||||
|
|
||||||
|
The Vagrant box will run all tests and report status in the output. If you
|
||||||
|
need to iterate through a fix/test cycle, tests can be re-run in a running
|
||||||
|
Vagrant box with:
|
||||||
|
|
||||||
|
.. code-block:: shell-session
|
||||||
|
|
||||||
|
# vagrant provision
|
||||||
|
|
||||||
Extra
|
Extra
|
||||||
-----
|
-----
|
||||||
|
|
||||||
Tags:
|
Tags:
|
||||||
If it's a bug that needs fixing in a branch in addition to Master, add a '\<release\>-backport-potential' tag (eg ``juno-backport-potential``). There are predefined tags that will autocomplete.
|
If it's a bug that needs fixing in a branch in addition to Master, add a '\<release\>-backport-potential' tag (eg ``juno-backport-potential``). There are predefined tags that will autocomplete.
|
||||||
|
|
||||||
Status:
|
Status:
|
||||||
|
@ -45,7 +63,7 @@ Importance:
|
||||||
Style guide
|
Style guide
|
||||||
-----------
|
-----------
|
||||||
|
|
||||||
When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format.
|
When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format.
|
||||||
|
|
||||||
Example YAML dictionary format:
|
Example YAML dictionary format:
|
||||||
.. code-block:: yaml
|
.. code-block:: yaml
|
||||||
|
|
|
@ -0,0 +1,9 @@
|
||||||
|
Vagrant.configure(2) do |config|
|
||||||
|
config.vm.box = "ubuntu/trusty64"
|
||||||
|
config.vm.provision "shell", inline: <<-SHELL
|
||||||
|
sudo su -
|
||||||
|
cd /vagrant
|
||||||
|
apt-get update
|
||||||
|
./run_tests.sh
|
||||||
|
SHELL
|
||||||
|
end
|
Loading…
Reference in New Issue