As 2023.1 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: I5b43a1a3061367a2d49b2d8dc10a06da6742bdaf
stable/wallaby is in EM state. As Tempest and
plugins masters does not support EM stable branches,
QA team is pinning tempest in devstack stable/wallaby
testing[1]. With that we do not need to test the
stable/wallaby jobs on master gate.
[1] https://review.opendev.org/c/openstack/devstack/+/871782
Change-Id: I3979f6e275f7b189546f4cc02e7db68238d77721
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: Ie8a57fa9e5ef8bef775b8ab78b7d04bceaf795ed
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: I5436b2f9a8e531490637c624ace5d2dc7412363b
stable/victoria is in EM state and Tempest is pinned
there so we do not need to test the stable/victoria
jobs on master gate.
Change-Id: I0930cdb342bd1c03a5ed405cf08efc587f244728
We have stable/yoga released and stable/ussuri is in
'Extended Maintenance' state. Current 'Maintained'
stable branches are yoga, xena, wallaby, and victoria.
As per tempest stable branch testing policy[1], adding the
newly released stable/yoga job and remove the EM stable/ussuri
job.
[1] https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I6efd637271247cc33880db6b3ac49243c299cdf9
We have stable/xena released so we should add
their job on master gate to keep branchless tempest
plugins compatible to stable branch.
This also removes the stable/train 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: I78a046f576a9fb666c11b8a15134dc46bb3537bf
We have stable/victoria and stable/wallaby released so we
should add their job on master gate to keep branchless
tempest plugins compatible to those 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: Ide464d5b64494050ff52f58832ed24bacecb83e9
1) Bump hacking max version to 3.0.1 and fix code style failures.
pep8 job is failing because the version of flake8 (flake8<2.7.0,>=2.6.0)
requested by hacking<1.2.0 is not compatible with pyflakes>=2.1.1.
Therefore the patch increases the max version of hacking.
2) Disable swift-proxy service which fails to start on stein. Disabled
other unneeded services while here.
Change-Id: I87c6d037fbbc24ef795ddbe26b5e297fb1bbc7a9
- move the base devstack jobs to blazar-tempest-plugin,
following the pattern used by other jobs, and make it
easier to use them on all branches;
- rename the jobs using the current convention;
- make the branch-specific jobs inherit from the base
(IPv4) job.
Change-Id: I30cf367a40620ce6c57d43df4be48a9a9d18ced6
Supported stable branches in maintenance state
(stein, train, ussuri) use the Tempest and plugins master
version for their testing. To make sure master version (new
tests or any changes) is compatible with stable branch testing,
we need to add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the stable
branches in same way[1].
Ussuri onwards, Tempest or plugins are py3 only, so we are
running only python3 version of stable jobs
Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
[1] e8f1876aa6/.zuul.yaml (L646)
Change-Id: Idc3791730eb5173d867254633152e51bc718b00c
There are installation and usage docs, but they are not published at
http://docs.openstack.org. Add the required job to publish them.
Change-Id: I1a68a42ee5eee45162565cca6bd3b1790e687296
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: I68575e1117ae5d3883b296e5e2ebf7d3f9b774ed
Story: #2002586
Task: #24286
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I6498f9808ef60e4550e3c6f33a0ab557e04948e9
Takashi Kajinami