Grenade jobs shouldn't get run on kilo, this got missed in the juno
symbol cleanup because the regex was a little specialized.
Change-Id: I23a29bc540163a936da285ee3bf37ae2fecb7694
Add another documentation directory "specs" to the filter.
The existing *.rst is enough for many cases but not always.
Change-Id: Idfb7fe873a9de37c3bdae005b7bed13281cf0bbb
Ironic now has a devstack plugin in tree. Make a job to be able to test
that it works, non-voting, before we actually switch everything over and
drop the devstack code.
Change-Id: I8724552e406c440bc7e9a589bf74992416dc9bae
Python 3 compatiblity was introduced in Liberty. There is
no point in running the python 3 jobs for Kilo.
Change-Id: I79ca1fd1335482cb54201db6f36aa2be2a2401a7
Python 3 compatiblity was introduced in Liberty. There is
no point in running the python 3 jobs for Kilo.
Change-Id: I0324ff4d4485b59e9f747602b8f83bbb4112dee7
So oslo.messaging 3.1.0 broke grenade, so trying to see
if these jobs would have caught the problem.
Change-Id: I958da05da99a2d451b980848d4fbb55f2d6681af
For document patches, these gates are not required:
gate-python-ironicclient-pypy
gate-tempest-dsvm-python-ironicclient-src
gate-ironicclient-dsvm-functional
So they will be skiped by this patch.
Change-Id: I8204450a79a37204d9223f1a5328e376954978e6
The non ha job has been tested on F22 and
F21 is going EOL. Also change the number of
F21 and F22 nodes appropriately.
Depends-On: I7835ec90d8bcbf1183b4217b9bc6d7714833d243
Change-Id: Ib42dbfc8e8ae1cf5e85159562bd6c112bc0d3220
Here we are just adding ansible-role-diskimage-builder and
ansible-role-jenkins-job-builder into the OpenStack gerrit workflow.
After talking with both openstack-infra and third party CI teams it
was decided to deal with which team this would be part of a later
date.
Additionally, we have not created a launchpad project for this module
or pypi (since we won't release there).
Gerritbot was also not configured at this time, since we don't know
which team we are going to be part of.
Change-Id: I18397f709059e3c4455f3fe9df2be08a6993fe7f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The change adds new projects for the roles within OpenStack-Ansible
This is the second batch for the break out work which encompases the
OpenStack-Ansible play `setup-infrastructure.yml`.
New projects:
- openstack/openstack-ansible-galera_client
- openstack/openstack-ansible-galera_server
- openstack/openstack-ansible-memcached_server
- openstack/openstack-ansible-pip_lock_down
- openstack/openstack-ansible-rabbitmq_server
- openstack/openstack-ansible-repo_server
- openstack/openstack-ansible-rsyslog_server
Governance Review: https://review.openstack.org/255372
Change-Id: Ia7509050693d81a4b3e01898ea4d5a6bfac3d598
Implements: blueprint independent-role-repositories
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
We only have a single voting multinode job, which is the grenade
partial upgrade job. Things like backportability of objects, and
actually going across a network get tested here in ways that no other
job tests. We should also use this test for requirements.
Change-Id: I9e6ff2e79ab1a59b7d1e4661b2f2030d8e453581
Publish the Python OpenStack SDK docs to
developer.openstack.org/sdks/python/openstacksdk
This needs a separate publish job for the publishing part.
Note: building is done with the usual docs job-template which is already enabled
via the python-jobs templates.
Closes-Bug: #1479977
Change-Id: I3eaffddc87c189df3e28d98a0154cdac381c62e8
No need to run functional, fullstack, minimal and unit tests jobs
reno patches. Change [1] exposed the permissive behavior so far.
[1] I59fcc217c5b8128840add1234aabc2687f3fa6a6
Change-Id: Id49437e144507fb61be2239778c719c7093dd887
This job was never used for its intended purpose and now there doesn't
seem to be much interest in having an automated, tested upgrade from
nova net to neutron. Since this isn't useful just remove it.
Change-Id: I55715461cb1691336352a364a5dad07c83b50fd0
To have the puppet integration jobs part of Health [1] project, we want
logstash about to read subunit-files.
So we need to rename the jobs to match this job filter:
job-filter: '.*(tempest|grenade)-dsvm.*'
That way, we will be able to see the subunit results on [1].
Puppet group already did the necessary to prepare the subunit files, we
just miss this patch to actually rename the jobs.
[1] http://status.openstack.org/openstack-health/#/
Change-Id: Ia41489a913d2adfc00b5f0d9177d1e810e95eec8