This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I0d8714cafb6a885bf42263cfecd481f2438b8912
Story: #2002586
Task: #24319
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
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
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Iad078d6502c1f72acf761f093ea8141d604bd2f3
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
This role is very special in that none of the functional tests are
voting.
Depends-On: https://review.openstack.org/588962
Change-Id: Ib26b42aa4d74beaecf9c06cc3114eee32fffb01b
The extra jobs that we have are not something that is needed, we simply can
set the jobs to non-voting in the project definition and avoid having non
voting jobs.
Change-Id: Iaaa440373172dcc89c052dbb7a0bfa2f876e0561
Given that the functional build for this repo
rarely passes and the repo itself is currently
unused, we can set the functional test to
non-voting in order to allow general pattern
changes to be implemented without delay.
This does mean that reviewers applying functional
changes will have to be disciplined about checking
the results, but I think that is OK in this case.
Depends-On: https://review.openstack.org/556253
Change-Id: I3f795e59f1b58862f2f196b2ac06d9891c3a17fa
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I31e6655743d3f69a84046978fe40f76021823cf3
Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: I8658108ad13cdc2fb2ff27e3079577f638cdbb11
This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
Change-Id: I3cb805ca067970033ba49f9ec5ef6c2db1fb8719
Guilherme Steinmüller