remove the tag pipeline entry for release-notes-jobs
We want projects to be using release-notes-jobs-python3, but most still have release-notes-jobs configured in their stable branches. Because tags are not branch aware, this means that we end up running two versions of the release notes publishing job when we tag releases. Those two jobs race, and at least one usually fails. By removing the tag pipeline entry from the older project template we avoid running two jobs for tag events, while continuing to use the older job when patches merge into older branches. See http://lists.openstack.org/pipermail/openstack-dev/2018-November/136214.html for more details. Change-Id: I34266e5629b1eac48c0defd64b03bba4a61eaf02 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
parent
887c5bf241
commit
e37568cc50
@ -274,9 +274,6 @@
|
||||
post:
|
||||
jobs:
|
||||
- publish-openstack-releasenotes
|
||||
tag:
|
||||
jobs:
|
||||
- publish-openstack-releasenotes
|
||||
|
||||
- project-template:
|
||||
name: release-notes-jobs-python3
|
||||
|
Loading…
x
Reference in New Issue
Block a user