Tempest use stestr to run the tests, adding
a experimental and periodic job to run Tempest
with stestr master will help to detect any
breaking change in advance.
Change-Id: Ice57e193c5150be7141e0e003be5091a191b854c
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
devstack-tempest and devstack-tempest-ipv6 jobs
are base jobs and other Tempest job like tempest-full-py3
or Tempest-ipv6-only are derived from those base job so running
tempest jobs are enough.
We do not need to run base jobs as such.
Change-Id: I2526b3bd5dc0d9a46ed15cefd941a3bbd55e6a49
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