we have stable/xena and stable/yoga also present
and supported so we should add their job on master
gate to keep branchless tempest plugins compatible
to stable branch.
This also removes the old EM stable branches which are
stein, train, ussuri, and victoria jobs.
Ref: Tempest plugins guide for stable branch testing:
Supported stable branches in maintenance state
(stein, train, ussuri) use the Tempest and plugins master
version for their testing. To make sure master version (new
tests or any changes) is compatible with stable branch testing,
we need to add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the stable
branches in same way.
Ussuri onwards, Tempest or plugins are py3 only, so we are
running only python3 version of stable jobs
Tempest plugins guide for stable branch testing:
 e8f1876aa6/.zuul.yaml (L646)
the reason which changes archive policy "bool" to "low" is that
the "bool" rule does not contain the default "mean" method.
At the same time, the "low" archive policy does not contain "last"
aggregation method, so we modify the default value of the
aggregation method to "mean" which supports all the strategies.
The parameter metrics have been added to make it easier
to modify the metrics for each strategy.
The job watcher-tempest-functional is voting in gate but non-voting in
check. This does not make sense, it needs to pass in check, otherwise it
will not pass in gate. Make the check job voting as well.
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
See the python3-first goal document for details: