opendev
/
infra-manual
Code Issues Proposed changes

Push PTI job config into projects 

The Infra team would like to avoid needing to review every PTI job
related update to openstack projects. Make it clear that it is ok for
projects to manage this config in repo so that they can manage and
review it themselves. This takes advantage of the new shiny features
that Zuul v3 provides in a way that should make both infra and
individual projects happier.

Change-Id: I51bd6c5bbcb8135c3ea4fed6941613643a3bcead
This commit is contained in:
Clark Boylan 2018-05-31 09:30:21 -07:00
parent 59da4b9e97
commit d7a44a9243
2 changed files with 21 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/source/creators.rst
View File

@ -551,6 +551,25 @@ gate pipelines. A minimal file that runs no tests includes only the
templates:
- noop-jobs
In the past we asked that official OpenStack projects manage the PTI job
config in the central projects.yaml file. This incurs review overhead
that Zuul v3 was specifically designed to push onto projects themselves.
In an effort to take advantage of this functionality we now ask that
projects manage the PTI job config in repo.
.. _central-config-exceptions:
Central Config Exceptions
~~~~~~~~~~~~~~~~~~~~~~~~~
There are several notable exceptions for job configs that should remain
in the central config repository:
* Translation jobs for all branches.
* Jobs that should only run against the master branch of the project
they are applied to.
* Jobs that are not "branch aware". Typically these are jobs that are
triggered by tag based events.
.. _add-to-governance-repo:

20
doc/source/zuulv3.rst
View File

@ -869,24 +869,8 @@ What to Convert?
~~~~~~~~~~~~~~~~
Some jobs should not be migrated and should always stay in `project-config`_.
- Official OpenStack projects should implement the OpenStack wide jobs
mentioned in the `Project Testing Interface`_ (PTI) document. These jobs
should remain in `project-config`_.
- Translation jobs should also live in `project-config`_, since those access
the external translation site.
So, a non-complete list of templates that should not live in project's own
configuration but stay in `project-config`_:
* announce-release
* check-requirements (PTI)
* openstack-python-jobs (PTI)
* openstack-tox-cover (PTI)
* publish-to-pypi (PTI)
* release-notes-jobs (PTI)
* translation-jobs
Refer to :ref:`central-config-exceptions` for up to date info on which jobs
should remain in centralized config.
Outside of these jobs, most jobs can be migrated to a project repository. If a
job is used by a single project then migration is simple: you should move the