Slawek Kaplonski 02c0b47d22 Promote neutron-ovn-tempest-slow job to be voting and gating ... This jobs is almost the same as tempest-slow-py3 since we switched OVN to be default backend in Neutron. And that tempest-slow-py3 job is used by many projects. So to avoid potential breaks of the gate for other projects (like we did recently, see related bug for details) let's make this job voting and gating. As it is really used in many different projects as voting and gating job already I don't think there is any issue with doing the same in the Neutron gate. Related-bug: #1936983 Related-bug: #1930402 Change-Id: I85d3830e9cc65162db846e4858871e1db547a04b		2021-07-21 08:57:43 +00:00
..
base.yaml	Merge "Make explicit the network backend used in the CI jobs"	2021-06-28 18:55:11 +00:00
grenade.yaml	Make explicit the network backend used in the CI jobs	2021-06-25 08:53:04 +00:00
project.yaml	Promote neutron-ovn-tempest-slow job to be voting and gating	2021-07-21 08:57:43 +00:00
rally.yaml	Make explicit the network backend used in the CI jobs	2021-06-25 08:53:04 +00:00
tempest-multinode.yaml	Merge "Make explicit the network backend used in the CI jobs"	2021-06-28 18:55:11 +00:00
tempest-singlenode.yaml	Merge "Use OVS backend for testing os-ken library"	2021-06-28 18:55:31 +00:00
tripleo.yaml	Configure branch on which tripleo jobs should be run	2021-04-09 17:01:20 +02:00