From 72923401f054bd47cf62c27b50f4a1aa3456ab14 Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Thu, 5 Oct 2017 19:10:50 +0200 Subject: [PATCH] Document which jobs should *not* get migrated Explain which jobs a project should not migrate. Change-Id: I112005d360f23648985d6691200d07476c622d70 --- doc/source/zuulv3.rst | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/doc/source/zuulv3.rst b/doc/source/zuulv3.rst index 4fa27d1..ab8ae4f 100644 --- a/doc/source/zuulv3.rst +++ b/doc/source/zuulv3.rst @@ -780,6 +780,28 @@ If those don't apply, this will mean the following changes: * Stop using nodesets prefixed with ``legacy-``. Each of them should have an equivalent non-legacy nodeset. +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 +thing. + +Official OpenStack projects should implement the OpenStack wide jobs +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 +configuration but stay in `project-config`_: + +* merge-check (system template) +* check-requirements (PTI) +* openstack-python-jobs (PTI) +* publish-to-pypi (PTI) +* release-notes-jobs (PTI) + +.. _Project Testing Interface: https://governance.openstack.org/tc/reference/project-testing-interface.html .. _Zuul v3 documentation: https://docs.openstack.org/infra/zuul/feature/zuulv3 .. _openstack-zuul-jobs documentation: https://docs.openstack.org/infra/openstack-zuul-jobs/ .. _openstack-zuul-jobs jobs.yaml: https://git.openstack.org/cgit/openstack-infra/openstack-zuul-jobs/tree/zuul.d/jobs.yaml