stable/zed has the new defaults and scope available but
they were disabled by default. Let's test those by enabling
in stable/zed also so that we know if they work fine in
integrated way or not
Change-Id: Id2bd58854f60f38dccf0ef805de284c7e95db2f3
Now we have stable/2023.1 branch ready for devstack
and so does for all service projects.
This commit adds the Tempest testing for stable/2023.1
by adding new jobs running on stable/2023.1 version of
openstack.
Change-Id: I5994c6fb56e01c9697d4d80bcbff2939ef2eff04
tempest-full-py3 job started using the new tox env
'integrated-full' which is not present in old
tempest used in stable/ussuri to wallaby. This
commit preapre a separate job definiton for stable
ussuri to wallaby which use 'full' tox env.
Closes-Bug: #2007986
Depends-On: https://review.opendev.org/c/openstack/devstack/+/874625
Change-Id: I5f1c4de0e7ec0cc6d7f6ba7d7aa78aabc931d23e
Recently we are seeing a lot of job timeout(bug#2004780)
and we see many tests taking time and also number of tests
increasing over time. This is to prepare the list of extra tests
(here extra tests means the tests which are covered by the other
API or scenario tests) which we do not need to run in every
integrated jobs. Instead, we can run them in a separete job(s).
Currently I am adding admin (except keystone) and negative tests
in the 'extra tests' list but we can add more tests here which
we think are covered in some other tests.
As negative tests are important for interop, adding those extra
tests coverage for stable branch job also but running them in
periodic run only.
Related-Bug: #2004780
Change-Id: Id02221df0d6180519751c63e890851bd59fdafa0
With patch I2e37603b098880b778100613800496b01167b22f some jobs based on
tempest-multinode-full-py3 on stein, train and ussuri branches started
to to run on Focal, howerer those run on Bionic previously.
This patch sets back to use Bionic for those branches.
Change-Id: I9c30cf332a419946516cba776b8a3ecdb3cbd3c2
As per 2023.1 cycle testing runtime and community goal[1] we need to migrate
upstream CI/CD to Ubuntu Jammy(22.04). Most of the Tempest jobs will be migrate
automatically once devstack base job start running on Jammy(Depends-On).
As we need to run at least one job on Ubuntu Focal(20.04), I am adding
a new job tempest-full-ubuntu-focal.
Few job like tempest-full-multinode-py3 and plugin sanity job needs to override
the nodeset. multinode job needs to run on Focal till stable/zed and on Jammy
from master(2023.1) onwards. Stable branch jobs testing stable branch needs to
keep running on their supported distro version which is Focal.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/860795
Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/861116
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: I2e37603b098880b778100613800496b01167b22f
Now we have stable/zed branch ready for devstack and so does
for all service projects.
This commit adds the Tempest testing for stable/zed by adding
new jobs running on stable/zed version of openstack.
Change-Id: I6a331a6f2466aa4e4d9f607660b87fa60a63bf4b
This marks the end of support for stable/victoria
which is EM now[1]. This remove the stable/victoria
jobs and also adds relesenote to mark the end of
support of Victoria.
[1] https://releases.openstack.org/
Change-Id: Ia63cdc682a32a2bcfd748f924368db6028b64d8c
To cover the stable branch testing on branchless Tempest
master gate, we test tempest-full version of stable branches.
Let's test the tempest-slow job also for stables branches.
All supported stable branches jobs are added in periodic
stable pipeline. As slow jobs are slow, it will make check pipelines
too heavy if we add all the stable branches slow jobs so
I am adding slow jobs only for the oldest supported stable job
which should cover the tempest master working on most
of the stable.
This will cover the Tempest slow tests stability for stable branches.
Change-Id: Idb8f178fa4fb4b669f3a163d5c5a9517b9d43c9a
This marks the end of support for stable/ussuri
which is EM now[1]. This remove the stable/ussuri
jobs which are failing due to bug#1968798 and also
adds relesenote to mark the end of support of Ussuri.
[1] https://releases.openstack.org/
Change-Id: Ieeb4da8859d44470c5cb67a62f2dcfd7786daf3a
Now we have stable/yoga branch ready for devstack and so does
for all service projects.
This commit adds the Tempest testing for stable/yoga by adding
new jobs running on stable/yoga version of openstack.
Change-Id: Id731c26a0f134428094e8d830fb615695dffe10b
Now we have stable/xena branch ready for devstack
and so does for all service projects.
This commit adds the Tempest testing for stable/xena
by adding new jobs running on stable/xena version of
openstack.
Change-Id: If6f188aebe48f17d8a343c958cdeb5507421a40b
Swift is ready on py3 since stable/ussuri and we enabled
it in tempest-full-py3 job for stable/ussuri onwards.
This commit does the same for tempest-slow-py3 job also so that
we can run swift slow test in this job.
Change-Id: I7fa41d4272f792d6fd00bece202c44e342dfeb0a
We have many job definition version for stable and master
gate and those are in same file integrated-gate.yaml. This
create confusion while modifying these jobs for master and
can end up modifying stable version.
Example: https://review.opendev.org/c/openstack/tempest/+/794312
Keeping all stable job definition in stable-jobs.yaml will help
us to accidentally modifying the stable jobs definition.
Change-Id: I44ae4a4b7070dd44f50070ad24e9d33f417ae955
Now we have stable/wallaby branch ready for devstack
and so does for all service projects.
This commit adds the Tempest testing for stable/wallaby
by adding new jobs running on stable/wallaby version of
openstack.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/784974
Change-Id: Ibb69384be54e284d59950371238a64c041348000
stable/stein is not suported in Tempest now, so
let's remove their jobs from master gate.
Also, update doc to reflect it.
Depends-On: https://review.opendev.org/c/openstack/stackviz/+/768212
Change-Id: I0cbc2883e1cfdb3b1d6b10a7ecea83a4bae32afb
Current .zuul.yaml file has 36 jobs definition and
it is growing more which makes it hard to read and
error prone.
This commit move the jobs definitions to zuul.d directory to
different yaml files:
- base.yaml includes base jobs definition
- integrated-gate.yaml includes integrated jobs to be
used in other openstack projects too.
- stable-jobs.yaml includes all stable jobs
- tempest-specific.yaml includes jobs supposed to run on Tempest
gate only
- project.yaml includes different pipelines (check, gate etc) definition
Change-Id: I984ecee81a9730b663764800f604333f28fd8180
Ghanshyam Mann