Ghanshyam Mann d7304b6416 Use publish-to-pypi-stable-only template for deprecated repo ... Deprecated deliverables only do the release on stable branches not on master. But existing publish-to-pypi template does not have the branch matcher to exclude the master gate from running the release jobs. For deprecated repo, we can use new template publish-to-pypi-stable-only which exclude the master branch to run the release jobs. This will help us to update the master conent which is README.rst for example: https://review.opendev.org/c/openstack/neutron-fwaas/+/800140 This also update the deprecdated repo description to add 'DEPRECATED'. And adding noop job for master branch so that we can merge the README.rst update for OFTC ref. Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/800554 Change-Id: Id6541db65e8b7957941c72d6d29474e07604adf0		2021-07-14 14:23:57 +00:00
..
jobs.yaml	Merge "Update Zuul job semaphore usage"	2021-06-28 22:00:25 +00:00
pipelines.yaml	Zuul: remove explicit SQL reporters	2021-02-15 15:26:48 -08:00
projects.yaml	Use publish-to-pypi-stable-only template for deprecated repo	2021-07-14 14:23:57 +00:00
secrets.yaml	afsdocs_secret-openstack-manuals: Zuul 4.6.0 fix	2021-07-06 19:01:21 +00:00
starlingx-jobs.yaml	Adds r/stx.5.0 to the list of branches to promote for starlingx docs.	2021-04-28 11:54:19 -07:00