From 211f3d4c705af37729260b9763195253e73a8cd2 Mon Sep 17 00:00:00 2001 From: Ghanshyam Mann Date: Wed, 21 Jul 2021 19:05:15 -0500 Subject: [PATCH] Document about using publish-to-pypi-stable-only for deprecated repo We have a new tempest publish-to-pypi-stable-only now which is used for the deprecated repo which still support stable branches. This commit document it in project-team-guide. Ref: https://review.opendev.org/c/openstack/project-config/+/800558 Change-Id: If4c73fe6a32f9e2a4f9841ab67aab05f7d76f6d3 --- doc/source/repository.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/source/repository.rst b/doc/source/repository.rst index 28cda0b..34d3944 100644 --- a/doc/source/repository.rst +++ b/doc/source/repository.rst @@ -113,12 +113,16 @@ Step 2a: Use only noop jobs Add ``noop`` jobs for master only in ``project-config`` repository and remove all templates temporarily with exception of -``official-openstack-repo-jobs``, it should look something like this:: +``official-openstack-repo-jobs`` and pypi release template if any. +If your project has ``publish-to-pypi`` template present, then change +it to ``publish-to-pypi-stable-only``. It should look something like +this:: - project: name: openstack/ templates: - official-openstack-repo-jobs + - official-openstack-repo-jobs + - publish-to-pypi-stable-only check: jobs: - noop: