From 51c3ea184accd56e535dbba4a6f2c0ff1210833d Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Mon, 27 Nov 2017 15:04:39 +0000 Subject: [PATCH] Fix release script for plugin latest_release We should never update the latest_release plugin on a PRERELEASE. We should always update it on a MAINLINE or BRANCH release. --- bin/release | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bin/release b/bin/release index b1b4e5bc..8849d725 100755 --- a/bin/release +++ b/bin/release @@ -196,7 +196,7 @@ publish() { if [ "$RELEASE_TYPE" = 'PRERELEASE' ] ; then echo "== Building and pushing plugin" - make UPDATE_LATEST=$IS_MAINLINE SUDO=$SUDO WEAVE_VERSION=$VERSION DOCKERHUB_USER=$DOCKERHUB_USER plugin_publish + make UPDATE_LATEST=false SUDO=$SUDO WEAVE_VERSION=$VERSION DOCKERHUB_USER=$DOCKERHUB_USER plugin_publish echo "** Plugin built and pushed" echo "== Tagging and pushing images on docker hub as user $DOCKERHUB_USER" @@ -232,7 +232,7 @@ publish() { echo '** Sanity checks OK for publishing tag' $LATEST_TAG as $DOCKERHUB_USER/weave:$VERSION echo "== Building and pushing plugin" - make UPDATE_LATEST=$IS_MAINLINE SUDO=$SUDO WEAVE_VERSION=$VERSION DOCKERHUB_USER=$DOCKERHUB_USER plugin_publish + make UPDATE_LATEST=true SUDO=$SUDO WEAVE_VERSION=$VERSION DOCKERHUB_USER=$DOCKERHUB_USER plugin_publish echo "** Plugin built and pushed" echo "== Tagging and pushing images on docker hub as user $DOCKERHUB_USER"