From f513ab5665044dfae98cddf6c4d3488dcff07c22 Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Fri, 6 Oct 2017 07:37:35 +0200 Subject: [PATCH] zuul v3: Mention translation jobs We should keep translations in project-config, document this. Change-Id: I79ec68b995c5acc431b6cc8007ffd00808c89ff0 --- doc/source/zuulv3.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/source/zuulv3.rst b/doc/source/zuulv3.rst index ab8ae4f..ece588f 100644 --- a/doc/source/zuulv3.rst +++ b/doc/source/zuulv3.rst @@ -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