Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add version, tag and branch checks to release script #11247

Merged
merged 1 commit into from
Oct 14, 2019

Conversation

jpbetz
Copy link
Contributor

@jpbetz jpbetz commented Oct 11, 2019

Improve checks in release script to prevent mistakes like the one I made in the etcd 3.3.16 release (#11241)

  • Before pushing the git version tag for a release version, check that the tag is on HEAD and that the tag is on the release branch. Do this check regardless of if the version tag is already pushed.
  • After pushing docker images pull them and run etcd --version and check that it reports the correct version.
  • After uploading release binaries, download them and run etcd --version and check that it reports the correct version

Fixes #11241

@jpbetz
Copy link
Contributor Author

jpbetz commented Oct 11, 2019

@YoyinZyc would you do a review pass on this as well?

Copy link
Contributor

@YoyinZyc YoyinZyc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good. Thanks Joe!

for IMAGE in "quay.io/coreos/etcd:${RELEASE_VERSION}" "gcr.io/etcd-development/etcd:${RELEASE_VERSION}"; do
local image_version=$(docker run --rm "${IMAGE}" etcd --version | grep "etcd Version" | awk -F: '{print $2}' | tr -d '[:space:]')
if [ "${image_version}" != "${VERSION}" ]; then
echo "Check failed: etcd --version output for ${IMAGE} is incorrect: ${image_version}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After finding out wrong image, can we remove it right away?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’d rather not. There are the production release builds. Deleting from them automatically comes with significant risk. If the script reports that they have the wrong version, I’d like a human to intervene and sort out what happened.

@YoyinZyc
Copy link
Contributor

LGTM, Thanks.

Copy link
Contributor

@gyuho gyuho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm thx

@gyuho
Copy link
Contributor

gyuho commented Oct 14, 2019

@YoyinZyc Can you help backport next week? Thx.

@gyuho gyuho merged commit 3ef2ad8 into etcd-io:master Oct 14, 2019
gyuho added a commit that referenced this pull request Oct 18, 2019
…47-origin-release-3.3

Automated cherry pick of #11247
gyuho added a commit that referenced this pull request Oct 18, 2019
…47-origin-release-3.4

Automated cherry pick of #11247
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

etcd 3.3.16 is a bad release
3 participants