openstack/project-config
Code Issues Proposed changes

if a release has been tagged, stop processing it

Browse Source 
When we were tagging releases by hand, sometimes the tag was applied
before any of the other processing was done. Now that all cycle-based
projects are using the release automation, we can skip updating
launchpad and the requirements repo if a release already exists.

Change-Id: I7c4a2c51dcba073b5b6d29ddf58fff1cb3f11055
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2016-12-07 08:20:58 -05:00
parent 5d14dacaeb
commit 7b859a974c
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
jenkins/scripts/release-tools/release.sh
View File

@ -66,11 +66,8 @@ PREVIOUS=$(get_last_tag $TARGETSHA)
echo "Tagging $TARGETSHA as $VERSION" echo "Tagging $TARGETSHA as $VERSION"
if git show-ref "$VERSION"; then if git show-ref "$VERSION"; then
echo "$REPO already has a version $VERSION tag" echo "$REPO already has a version $VERSION tag, skipping further processing"
# Reset the notion of "previous" to the version associated with exit 0
# the parent of the commit being tagged, since the tag we're
# applying already exists.
PREVIOUS=$(get_last_tag ${TARGETSHA}^1)
else else
# WARNING(dhellmann): announce.sh expects to be able to parse this # WARNING(dhellmann): announce.sh expects to be able to parse this
# commit message, so if you change the format you may have to # commit message, so if you change the format you may have to