If a change had a -1 verified vote on it from jenkins zuul would not
enqueue that change for check or gate testing when that change was
approved. Zuul should enqueue the change for check testing then move it
to the gate pipeline if a verified +1 comes back from check.
Change-Id: Icdcc4878a8289a2088c85afdfc72c56d4fd3a55a
There was an error in the conditional due to spacing (no space after the quotes). To fix
it I decided to replace the conditional with simpler 'mkdir -p' command.
Change-Id: I0f83e2823c69c5f9e3427e0925335e54e9b6c2a0
These are projects we'll want symmetric gating on eventually, and a
new pipeline allows us to work up tests and make sure things are
working properly in advance of having a sufficiently high uptime cloud
with fast enough tests to be in the main experimental queue.
Change-Id: Ic6369910ba162648608e17ec2c4057dc982120f5
This reverts commit 794b1d4e89e5d38de729f362334830706ba08c09.
The new pipeline makes running these jobs again feasible.
Change-Id: I6ebed8a5003424e5ac34cc08ca4dd93230175a1a
The experimental-tripleo pipeline is to enable building out tripleo
tests against other projects in advance of the second region coming
online.
The check-tripleo pipeline ensures that in the event of a tripleo
cloud failure the main check queue won't appear to backlog, making
analysis of devstack-gate check health easier.
Change-Id: I93045879c508defd4f1f86979fb42da79bd29fad
Add check, gate, post and release jobs to PHP/Laravel based openstackid
project. Extend precise node with php5-mcrypt package required for
build process.
Change-Id: If7858412d5c3425aab20c0d11a92cab4c86f47dd
The previous change to switch to py3k-precise nodepool nodes
overlooked that the old static precisepy3k slaves had on them cruft
Python 2.7 installs of setuptools which worked with pypy. Switch
back to them for now while we work on solving that issue.
Change-Id: I6899035d0c422f622699f6729f573d16e4a9bc91
The regex that set reusable node on proposal node jobs did not match the
names of the requirements proposal jobs. Edit the regex so that it
matches.
Regex should match: propose-requirements-updates
but would only match .*-propose-requirements-updates.
Change-Id: I5445bf416c407b0deb6229c3e022e69af93e4dea
If a change ends up with a +2 from jenkins but no approval (because
a core reviewer removed his or her vote), allow it to be enqueued
the next time someone approves it.
Change-Id: I0d21921ac6bfbf93fb136bba8e921f2257f57567
We are still bootstrapping oslo.vmware and seeing various
errors in requirements and documentation. Please switch
these off for a few days so we can get the first set of
patches merged and get us off the ground
Change-Id: I86ebe1df73e91fcd55d08979020e0648e2480720
Strictly speaking, we only need sync calls at the end of the
script that is directly invoked by nodepool. But just so we
don't have to think about it too much, add them to all prepare
scripts.
Without it, clouds will happily snapshot a system without all
the data written to disk!
Closes-Bug: 1282136
Change-Id: Id7dcf6667d6e48eb5ae95fd42b09f0651eeb38f9
* modules/openstack_project/files/zuul/layout.yaml: The
propose-requirements-updates job name is plural, unlike other
propose-.*-update jobs, so add an optional s? at the end of the
pattern. Without this, proposal.slave.openstack.org gets set offline
every time that job is completed.
Change-Id: I0f7d8366a094666945af7387dba3623b393e9659
Change all jobs to openstack-doc-tools setup.
Introduce new job template '{name}-tox-doc-{envlist}' that is
used for all api jobs that publish to docs.openstack.org.
Introduce new publishers 'upload-to-docs-site' and 'upload-to-api-site'.
The job names are changed as follows:
* openstack-api-quick-start -> api-site-tox-doc-publishdocs
* openstack-api-ref: Converted from maven to freestyle.
* block-api-v2.0 -> volume-api-tox-doc-publishdocs
* compute-api-v2.0 -> compute-api-tox-doc-publishdocs
* identity-api-v2.0, identity-api-v3 -> identity-api-tox-doc-publishdocs
(handles also api v3)
* image-api-v1.1, image-api-v2.0 -> both handled by
image-api-tox-doc-publishdocs
* network-api-v1, network-api-v2 -> netconn-api-tox-doc-publishdocs
* object-api-v1.0 -> object-api-tox-doc-publishdocs
ATTENTION root team:
This changes openstack-api-ref from maven to freestyle. Please delete
openstack-api-ref after approval so that it gets recreated correctly.
Change-Id: I8b91bfa462224f0e6114ce2b8cb80942810b0a0e
Switch to running python33 and pypy unit tests on py3k-precise nodes
once Ic03b9532ec0ad8b6abe8171855e6c33f7dcffef2 merges and the
additional images/nodes are ready for action.
Change-Id: I98ad3a1171034cda1236dbb6dbfaddc2e26934cf
* .../files/nodepool/scripts/prepare_node.sh: Add parameters for
Python 3 and PyPy settings for use by the py3k-precise node type.
* .../files/nodepool/scripts/prepare_node_py3k.sh: Wrapper to enable
the Python 3 and PyPy support toggles in prepare_node.sh.
* .../manifests/single_use_slave.pp: Add the Python 3 and PyPy
support variables, passing them through to the Jenkins slave class.
* .../templates/nodepool/nodepool.yaml.erb: Add a new node and image
for py3k-precise in a suitably small quantity for initial testing.
Change-Id: Id2438c17ea59ae9123a841fd0b348728c6467529
* doc/source/jjb.rst
* doc/source/stackforge.rst: Update examples to recommend
bare-precise nodes in new job configuration.
* modules/openstack_project/files/jenkins_job_builder/config/*.yaml:
Change the node label for all jobs opreviously using precise to use
bare-precise instead.
* modules/openstack_project/files/zuul/layout.yaml: Get rid of the
transitional matches for setting the single use parameter function
on specific job names and just set it on everything as a default.
Add patterns for jobs which need long-running slaves to apply a
reusable node parameter function instead.
* modules/openstack_project/files/zuul/openstack_functions.py: Add a
parameter function for reusable nodes which refrains from enabling
auto-offline behavior.
* modules/openstack_project/templates/nodepool/nodepool.yaml.erb:
Double the minimum ready bare-precise nodes to accommodate
additional load.
Change-Id: I2a90c5b120a50bb8033c891702185f054ee84d35
pycadf is adding a dependency to oslo.messaging. because of this,
python33 gate is failing due to lack of py33 compatibility in
oslo.messaging. oslo.messaging has no intention of py33 support for
Icehouse so let's drop the gate for now
Change-Id: I7c7082829de99dd299028a159bbeeef2eceac772
We already have a bunch of CLI tests merged into the tempest, so, we'd
like to add python-savannaclient to small savanna 'pipe'. Additionally,
we're going to write some scenarios tests, so, it'll add some tests for
client too.
Change-Id: I38887088077137ba071622f3e1d6d9b353cbebd4
This reverts commit 084f24b3fc94312c420743b3e5aaa7b5e5c29ea3.
The tripleo cloud was down again. Remove jobs that require it
until it is more stable, we are better able to handle a lack of
stability from cloud providers, and we are outside of the i3
rush.
Change-Id: Idde131380284fcb905241559b08691456310092a
Since the neutron jobs were fixed to enable tenant isolation we don't
have any runs the non-isolated path. Since this is supported tempest
configuration we need to ensure that things don't bitrot. This commit
adds a periodic full non-isolated serial job to test this
configuration.
This depends on devstack-gate change:
Ida532021e1287efed09343e8e546d0605355e889
Change-Id: Ib41f0662e63a76aa6bd9a697db1d2f6122630533
We're planning to add CLI and scenarios test to Tempest, so, we should
be able to see jobs running them.
It's partially reverts Ia4cd9106033fbfada5f0cbf8c38d07d0e915edb0
Change-Id: I9473a57e1ca8df119312bd2e3725736c5b00d288
