Move the puppet-openstack-integration-nv rule prior to the stable/kilo
restriction, otherwise the jobs will run everywhere and we don't want
that. We want them to run only after Mitaka or Jewel (current master).
Also document the stable/kilo rule, so we won't do this mistake next
time.
Change-Id: I170a548c66b948ecf2ec70972e1066c314cc3756
To test rally scenarios for magnum we need CI jobs.
Add a job and a builder for magnum to rally.
Change-Id: Iac88b84d48582083f7c3f47a71302913f52aac7b
Partially-implements: blueprint benchmark-scenarios-for-magnum
Currently no job is configured to publish Tricircle package to
PyPI. Now the Tricircle package index has been registered in PyPI site
https://pypi.python.org/pypi/tricircle, and 'openstackci' has been
added to the owner role. This patch is to add job to publish Tricircle
package to PyPI.
Change-Id: I63ddee9e6dca20466aaf0b6b3c498fb550b15a5c
Signed-off-by: Chaoyi Huang <joehuang@huawei.com>
Change layout ordering so:
* Xenial jobs will only run after Mitaka / Hammer
* Trusty jobs will only run for Mitaka / Hammer and before.
Change-Id: I89c2cc903af5a7cf15de09bb406819d022f399ba
Requirements of the python-oneviewclient package should be consistent with
Ironic's. This patch ensures that it'll be checked against global-requirments.
Change-Id: Ia32d66aa7af07f69e1dfd2c28bc8ca96c0832376
In a previous patch, we missed to support stable/hammer branch for
puppet-ceph, which is following the same testing as Mitaka release.
Change-Id: I91fdb09b1bc5af1e333e768d053c0addd69dfcf0
This patch adds a new job to run devstack on dsvm for higgins.
Nothing test added yet, just for testing higgins service works well.
Change-Id: I3c2c764da76f7be5432d796d2b2280217f13052b
Depends-On: I55542a1522121b9504f8018ce682be9b874fa941
Integration jobs are now working with a few workarounds that we are
going to fix during Newton cycle.
This patch moves the Xenial integration jobs from experimental pipeline
to check & gate.
On Kilo, Liberty, Mitaka, Hammer (ceph): keep trusty jobs and do not run
xenial jobs.
Starting from Newton (current master) and Jewel (ceph): run & gate on xenial jobs.
Change-Id: I670d9e4a581333004b622abebde03414e957dbdf
Puppet OpenStack group has the desire to run puppet4 jobs as non-voting
in the check pipeline for openstack/puppet-openstack-integration
project.
This patch:
* remove puppet4 periodic jobs.
* create puppet-openstack-integration-jobs-puppet4-check-nv with all
puppet4 jobs in the check pipeline.
* create puppet-openstack-integration-jobs-puppet4-experimental with
all puppet4 jobs in the check pipeline.
* Use puppet-openstack-integration-jobs-puppet4-check-nv in
openstack/puppet-openstack-integration layout, starting from Newton /
Jewel.
* Use puppet-openstack-integration-jobs-puppet4-experimental-nv in
Puppet modules layouts that use puppet-openstack-integration-jobs-all.
This is an iteration for us to move to Puppet4 gating.
We started the work with experimental jobs, then periodic jobs and now
check jobs.
Once we stabilize puppet4 jobs, we'll add them in the gate pipeline.
Change-Id: Ie2214d9a46435b7073640974c13709f55760897c
We've recently noticed that some patches in Tempest used to break
downstream CIs like Puppet OpenStack, because we deploy in another way
than Devstack:
http://git.openstack.org/cgit/openstack/puppet-openstack-integration/tree/README.md
We used to have Puppet jobs part of experimental pipeline for Tempest
testing but this is not enough.
This is a proposal to run Puppet jobs in the check pipeline, as
non-voting. The jobs will bring valuable feedback in the future without
slowing down Tempest testing (3 jobs, ~30 minutes each).
Change-Id: I46ea5b0cf0e52a0ddc6bac14d1db4a42ae79a1bb
Add a non-voting py34 job for zuul so that work towards py3 zuul
can occur with initial reporting progress towards passing checks.
This can be converted to a voting job once the gate is passing with
py34.
Change-Id: I35a8e3a00b440844ab00d707fbc0174dd7ba1b8b
In order to facilitate the execution of the release announcements for
OpenStack-Ansible repositories (which don't publish tarballs), this
patch sets up the announce-release post job for a selective set of
repositories.
Also included is a small fix to the experimental jobs for the os_aodh
repository.
Change-Id: Ia56d236d3a952f9370a0c23622ec08d62f0e287b
pxe_libvirt driver has moved to ironic-staging-drivers, so the job
should be added there at some point.
Change-Id: I33d7d82bdeb7fc424b3ebb663b39a7d9a0e7f0d3
CentOS-7 & Ubuntu-Xenial support in OpenStack-Ansible roles has
only just been introduced in the Newton cycle.
This patch aims to skip those Ansible role jobs for the 'liberty'
(yes that is the correct name) and 'stable/mitaka' branches.
Example jobs which should be skipped:
- branch: liberty
repo: openstack/openstack-ansible-security
job: gate-openstack-ansible-security-ansible-func-centos-7-nv
- branch: liberty
repo: openstack/openstack-ansible-security
job: gate-openstack-ansible-security-ansible-func-ubuntu-xenial-nv
- branch: stable/mitaka
repo: openstack/openstack-ansible-os_keystone
job: gate-openstack-ansible-os_keystone-ansible-func-centos-7-nv
- branch: stable/mitaka
repo: openstack/openstack-ansible-os_keystone
job: gate-openstack-ansible-os_keystone-ansible-func-ubuntu-xenial-nv
Example jobs which should execute:
- branch: master
repo: openstack/openstack-ansible-security
job: gate-openstack-ansible-security-ansible-func-centos-7-nv
- branch: master
repo: openstack/openstack-ansible-security
job: gate-openstack-ansible-security-ansible-func-ubuntu-xenial-nv
- branch: master
repo: openstack/openstack-ansible-os_keystone
job: gate-openstack-ansible-os_keystone-ansible-func-centos-7-nv
- branch: master
repo: openstack/openstack-ansible-os_keystone
job: gate-openstack-ansible-os_keystone-ansible-func-ubuntu-xenial-nv
Change-Id: I3bf20c3f168ce110b810a7901e920e5f5799078e