metalsmith/playbooks/integration
Julia Kreger e0ed4d2dee Rework jobs so failed devstack does not retry the job
Per clarkb, should any step in pre.yaml fail, zuul presently retries
the entire job up to the built in retry limit which cannot be changed
or disabled on a job basis. In the terms of setting up devstack, this
is not ideal as devstack is not perfect and can often fail for unrelated
reasons such as package mirrors being updated or even another project
or component failing to setup properly.

As such, in order to be good neighbors and minimize the amount of
time it takes to troubleshoot such issues, we need to move the
devstack setup into the main part of the CI job.

Change-Id: I08d6f3132ebc045ba7e2d1295efe39af7c57187c
2020-09-09 11:32:51 -07:00
..
centos-image.yaml Rework jobs so failed devstack does not retry the job 2020-09-09 11:32:51 -07:00
cirros-image.yaml Always use the latest cirros image 2019-01-15 10:22:55 +01:00
exercise.yaml Completely switch to openstacksdk 2019-01-15 10:24:52 +01:00
initial-setup.yaml Rework jobs so failed devstack does not retry the job 2020-09-09 11:32:51 -07:00
post.yaml Add the "---" into ansible yaml file 2018-09-16 01:41:07 -04:00
run.yaml Rework jobs so failed devstack does not retry the job 2020-09-09 11:32:51 -07:00
ssh-key.yaml Add the "---" into ansible yaml file 2018-09-16 01:41:07 -04:00