zuul v3: Mention translation jobs
We should keep translations in project-config, document this. Change-Id: I79ec68b995c5acc431b6cc8007ffd00808c89ff0
This commit is contained in:
parent
72923401f0
commit
f513ab5665
@ -784,7 +784,7 @@ What Not to Convert?
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Note that some jobs should always stay in `project-config`_. We always
|
||||
like to have merge-check in `project-config`_, since that's a system
|
||||
like to have ``merge-check`` in `project-config`_, since that's a system
|
||||
thing.
|
||||
|
||||
Official OpenStack projects should implement the OpenStack wide jobs
|
||||
@ -792,7 +792,10 @@ mentioned in the `Project Testing Interface`_ (PTI) document. These jobs
|
||||
should remain in `project-config`_ but all the other things (things
|
||||
special to a given project) can happen in the project repository.
|
||||
|
||||
So, a non-complete list of jobs that should not live in project's own
|
||||
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`_:
|
||||
|
||||
* merge-check (system template)
|
||||
@ -800,6 +803,7 @@ configuration but stay in `project-config`_:
|
||||
* openstack-python-jobs (PTI)
|
||||
* publish-to-pypi (PTI)
|
||||
* release-notes-jobs (PTI)
|
||||
* translation-jobs
|
||||
|
||||
.. _Project Testing Interface: https://governance.openstack.org/tc/reference/project-testing-interface.html
|
||||
.. _Zuul v3 documentation: https://docs.openstack.org/infra/zuul/feature/zuulv3
|
||||
|
Loading…
Reference in New Issue
Block a user