if a release has been tagged, stop processing it
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:
parent
5d14dacaeb
commit
7b859a974c
@ -66,11 +66,8 @@ PREVIOUS=$(get_last_tag $TARGETSHA)
|
||||
|
||||
echo "Tagging $TARGETSHA as $VERSION"
|
||||
if git show-ref "$VERSION"; then
|
||||
echo "$REPO already has a version $VERSION tag"
|
||||
# Reset the notion of "previous" to the version associated with
|
||||
# the parent of the commit being tagged, since the tag we're
|
||||
# applying already exists.
|
||||
PREVIOUS=$(get_last_tag ${TARGETSHA}^1)
|
||||
echo "$REPO already has a version $VERSION tag, skipping further processing"
|
||||
exit 0
|
||||
else
|
||||
# WARNING(dhellmann): announce.sh expects to be able to parse this
|
||||
# commit message, so if you change the format you may have to
|
||||
|
Loading…
Reference in New Issue
Block a user