commit a9bad0051255327e0a0456a0d46c34f1a6ed4c79
Author: Ghanshyam Mann <email address hidden>
Date: Wed Feb 8 14:13:48 2023 -0600
Move a few jobs to periodic
We have a few jobs running gate even they are non voting
and run in periodic as well. They do not need to run in
every change but running/checking them in periodic run
is enough coverage. Below are the jobs moving to periodic:
* tempest-full-py3-ipv6
We do run tempest-ipv6-only job as voting in gate to
cover the ipv6 run and tempest-full-py3-ipv6 job can
run perdiocially to test the full tempest on ipv6.
*tempest-full-centos-9-stream
we already discussed and agreed in TC also that centos stream
testing is best effort and can be in periodic or non voting.
*tempest-full-test-account-no-admin-py3
Checking if tempest can be run without admin in periodic and not
on every change is enough.
* tempest-full-yoga
We do run all supported stable branch jobs periodically and running only
latest and oldest supported in check pipeline should be enough to catch
any breaking change on stable branches.
Reviewed: https:/ /review. opendev. org/c/openstack /tempest/ +/873163 /opendev. org/openstack/ tempest/ commit/ a9bad0051255327 e0a0456a0d46c34 f1a6ed4c79
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit a9bad0051255327 e0a0456a0d46c34 f1a6ed4c79
Author: Ghanshyam Mann <email address hidden>
Date: Wed Feb 8 14:13:48 2023 -0600
Move a few jobs to periodic
We have a few jobs running gate even they are non voting
and run in periodic as well. They do not need to run in
every change but running/checking them in periodic run
is enough coverage. Below are the jobs moving to periodic:
* tempest- full-py3- ipv6 full-py3- ipv6 job can
We do run tempest-ipv6-only job as voting in gate to
cover the ipv6 run and tempest-
run perdiocially to test the full tempest on ipv6.
*tempest- full-centos- 9-stream
we already discussed and agreed in TC also that centos stream
testing is best effort and can be in periodic or non voting.
*tempest- full-test- account- no-admin- py3
Checking if tempest can be run without admin in periodic and not
on every change is enough.
* tempest-full-yoga
We do run all supported stable branch jobs periodically and running only
latest and oldest supported in check pipeline should be enough to catch
any breaking change on stable branches.
Relavant-Bug: #2004780 64ce3cc39115c1d 807b21fff95
Change-Id: I8a2da7288e3f22