The stable/2023.2 branch was cut off a while ago. Also the stable/yoga
already entered the EM phase so does not require testing.
Change-Id: I959aded71235ca8577733696f25ec8b891d925e0
As 2023.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Also removing EM stable/xena|wallaby job
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I80213eb072281ec0a71fa068f9d8f25d0feffe27
As zed is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I10bbcdf711ede18496545e6a4b1fd1098388e891
In 2023.1 cycle. we are moving the default distro
version of Ubuntu to Jammy (22.04)[1] so we need to pin
the nodeset for stable branch job in master gate so that
they continue run on their supporting distro version which is
Ubuntu Focal since stable/victoria.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: I5f4f1338a60634af8ae062475e314feb55c4a26d
... because the broken integration job in master has been fixed.
Depends-on: https://review.opendev.org/851670
Change-Id: I9a83d4d7c906e89be93d441a44cd159aa6d694a3
Nova requires the public_key element when creating a keypair since api
version 2.92. This change ensures the element is passed when creating
a OS::Nova::KeyPair resource.
The master jobs are temporally made non-voting because one integration
test is failing now. These jobs are made voting again once the test is
fixed in the heat repo.
Story: 2010201
Task: 45921
Change-Id: Icdc25a7a79f02ccc5eadcfa5dee99ce5f4d3b00e
we have stable/xena and stable/yoga also present
and supported so we should add their job on master
gate to keep branchless tempest plugins compatible
to stable branch.
This also removes the old EM stable branches which are
train, ussuri, and victoria jobs.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I56aaabe6d4a228dfc9434e9d0c163251ff64c279
Currently functional jobs are all broken because of recent bump of
cinder client. Since we need fix for both heat and heat-tempest-plugin
repo this change first make all functional jobs non-voting to unblock
any change in heat-tempest-plugin repo until the fix is merged in heat.
Change-Id: Icf20b3c07588ee287b106a924580fd6aead4d4e4
We have stable/wallaby released so we should add
their job on master gate to keep branchless tempest
plugins compatible to stable branch.
This also removes the stable/stein job as that is in EM
state now.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I9c36e08e8d8e27a97605466953fa79b799fae341
stable/queens and stable/rocky are in extended maintainance state
and devtack use the older Tempest version to tests them not the master.
Testing them on master gate is not needed as heat-tempest-plugin master
cannot support testing them due to python required version for plugin
and Tempest. Even we test them on master gate, they run with older Tempest
so they are not actually testing the master code against those stable.
We can continue testing the supported stable branch where master Tempest and
plugins are used.
Same is done Tempest and other plugins side:
- https://review.opendev.org/#/c/722183/
- https://review.opendev.org/#/c/707111/
Change-Id: I3dd3c354947461ba65906251fb42897b0b8ce6f5
We have migrated our testing from Xenial to Bionic
since stein. Xenial node is not supported on stein onwards.
Any job running on stein onwards should use the bionic nodeset.
Change-Id: If8a018465f6ed3ec5c35c0934370c1107f4b9969
We run check jobs against stable/queens. Also run them against
stable/rocky now that Rocky has been released.
Change-Id: I3e311048cd983c7f125ae099dbb08836c658ded3
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I49c3912a6eed81d896442e012354efe952aa2000
Story: #2002586
Task: #24298
We're moving the non-apache job to non-voting in heat, so remove it
from the gate jobs in the tempest plugin too.
Depends-On: https://review.openstack.org/567459
Change-Id: Id7225942795507c7b0c5001889209617cdf8934e
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I897b82a12198ab951ebad99e3bdf59314ec4e936
Takashi Kajinami