add an update voting job to mimimal check
At the moment tripleo-upgrade is ungated.
To properly protect against changes in tripleo
repos it is useful to run the update job as
voting to help detect if a tripleo change
caused the update job to fail.
Related-Change: https://review.openstack.org/#/c/565523/
Change-Id: Iecdaf0af05d8810738785d6e858b281aff9aba29
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I67d2ab519d1baf463e4ad253b8a85b5194ad31f6
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
When making changes in deployed-server configs it should be tested
with all current multinode jobs to prevent their breakage.
Change-Id: Ic32b01f9b63150593941399cb76ffd3831e9c716
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I58bfd094134e2c39d046ecc55a74b940db014bf8
Jobs now run in RDO CI, we don't need RH1 cloud to run OVB jobs anymore.
We'll keep experimental jobs until a complete decomission.
Related-Bug: #1744763
Change-Id: I25dcc22563316e184577822609aa7457da1c1d12
Jobs are passing now, let's re-enable it.
This reverts commit 39c6233306b71406c28f584bdac8bac388ce0b1c.
Change-Id: I386b0a6289eb4049326c805583f064fc99c19be0
This reverts commit 761a809292c8f3bde7e7a68e19a9af7d20a65fba.
It's still broken so it's just non-voting in the gate, let's
revert this until we actually fix scenario002. This change
should have been depends-on the tripleo-ci change that switched it back to voting.
Change-Id: Id2a1f94eaf0d58c1fa87aaa04e57fc54cfb8a212
All scenarios run Pacemaker now, so we need to test every change in
the pacemaker services too.
Also removing pingtest files for the scenarios that run Tempest.
Change-Id: I6da9687fad62ff5116cee50683c1deb534b80507
This is a partial revert, scenario002 is now failing on Tempest.
This reverts commit 309e409c37ceca2c5450ffbc49ddb4241f5c4305.
Change-Id: I5c8c8e75aba8cded9a5a91e3030b2e591ef2a444
scenario001 is timeouting a lot while scenario 007 is fine and far from
timeout limit, so moving out services.
Change-Id: Id34321f95a0584cbc9f6e40f3cd47ed0386cfc9d
CI is very unstable now but we need to merge some patches
so we can get promotion and hopefully stabilize CI.
Change-Id: Iffbb2da53221efe6f014f245316c66913ff8c648
It was a bad idea because now we run ovb-ha only when we touch this
file. We don't want that. In fact, we have a irrelevant-files list in
tripleo-ci that we should improve if we know some files that have no
impact on ovb-ha.
This patch remove the file rule, so we run the job again on THT unless a
patch only touch irrelevant-files.
Change-Id: I7a2f8791bf52c2251bd8e13100fd2d50632008fc
We've seen it passing, time to move from experimental to non-voting
check job. It's still restricted to run only on changing the specified
files.
Change-Id: I265fc10c4b7e30261fc783610b8e1e08ef928bc1
Add an environment that deploys a basic overcloud:
- Pacemaker to test HA on 3 controllers
- Keystone, Glance, Nova, Neutron, Swift
Also change the zuul layout to run ovb-ha scenario when
touching ovb-ha.yaml file.
Change-Id: I865901f38250a13d8ea914a54072d6eb584a050d
Define the zuul v3 layout for jobs that we want to execute.
Change-Id: I149322f4b6d5c066eb345618445143df43607765
Depends-On: Ie8aa85fe7a8ee556cc1b46e215d329e95913290c