Since we copy all release notes to the integrated repo there is not need
in publishing release notes for each repository. We should only verify their
validity and linting.
Change-Id: I36ee9b464c1418f9f013169c13ce8b0c6c3f4fcd
Currently this role doesn't test the integrated jobs.
With the dynamic execution of the roles, this role
also get tested by the integrated repo.
Change-Id: I3777ded4ca030ddf3d9e27b11cc1e830e2b54592
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: Ia9ceef821bfd2a356f4c111c9de49796eab7b999
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: Id461e3b9c52fb835ed4fe3be37f01a216d9253b6
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Change-Id: Idd5969b1d36bd1a10fe498629d17c2065d818ab3
Now that bionic testing is added into the tests repos, we can
start testing it in the repo.
Depends-On: https://review.openstack.org/#/c/566959/
Change-Id: I82b6a9c54eacb9b0b5e93fb428c105b19840ef65
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I373258e1b2147a53f1275a4679d7a55cb4b28fc3
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: I1e0a7e26491ad4086835c0f1bf26cfc86b5378fe
Currently the linters test is in the project-config
repository, but those are meant to be used for standard
jobs which do not require any repository other than the
one given. Our lint tests use the 'openstack-ansible-tests'
repository, so we should rather use our own job definition.
Change-Id: Ifae2d7dc08713e1c92218a207f19f856b0b5811a
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
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.
Change-Id: I8cae14c37422a5eb4b9580b0a8220ddfa5cb6053
Dmitriy Rabotyagov