tree 54c2f4f9175bf21740ae0381f0e2bd3465857c65
parent e9c2248e1522ee95fd65caab5844b10e00ef5bb1
author Ghanshyam Mann <gmann@ghanshyammann.com> 1675887228 -0600
committer Ghanshyam <gmann@ghanshyammann.com> 1676142301 +0000

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.

Relavant-Bug: #2004780
Change-Id: I8a2da7288e3f2264ce3cc39115c1d807b21fff95