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

build: Publish GitHub tag in release script #51

Merged
merged 1 commit into from
Aug 30, 2022
Merged

Conversation

brianluong
Copy link
Member

@brianluong brianluong commented Aug 30, 2022

Description

As discussed in launch last Friday

Type of change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • 😎 New feature (non-breaking change which adds functionality)
  • ⁉️ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • ⚒️ Refactor (no functional changes)
  • 📖 Documentation (updating or adding docs)

How Has This Been Tested?

image

image

Also

Commented parts of the script out to test IsProductionRelease

➜  node-gateway git:(publish_github_tag) ✗ ./scripts/release.sh b9147f3309d8cdcd09533265016c3aaa8dc78735 0.1.0 dianwen/satsuma-gateway-test
➜  node-gateway git:(publish_github_tag) ✗ ./scripts/release.sh b9147f3309d8cdcd09533265016c3aaa8dc78735 0.1.0 satsumaxyz/node-gateway

Have you already tested this image by pushing it up to the satsumaxyz/node-gateway Docker registry? [y/N] y

@brianluong brianluong force-pushed the publish_github_tag branch 2 times, most recently from 2e7911d to 50fb270 Compare August 30, 2022 15:45
@dianwen
Copy link
Member

dianwen commented Aug 30, 2022

Looks great! Mind updating the release docs?

@@ -91,6 +96,14 @@ make VERSION=$RELEASE_VERSION GIT_COMMIT_HASH=$COMMIT_HASH build-archives
LogStep "Building and pushing the image."
make GIT_COMMIT_HASH=$COMMIT_HASH DOCKER_HUB_REPO=$DOCKER_HUB_REPO VERSION=$RELEASE_VERSION build-and-push-image

if IsProductionRelease
Copy link
Member Author

Choose a reason for hiding this comment

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

Added this flag to push tag only on production release

@brianluong
Copy link
Member Author

brianluong commented Aug 30, 2022

Looks great! Mind updating the release docs?

I updated this doc here, but the update was very small: #51 (comment)

"After the release script finishes, create a GitHub release for the commit with the version as the tag (following the format v0.1.0). This tag was just pushed by the release script. Upload the archives created by the release script and write release notes."

Bold = new stuff

Copy link
Member

@dianwen dianwen left a comment

Choose a reason for hiding this comment

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

Good stuff!

Should we change L113 to say something to the effect of "select the tag with the release version"? It still kinda sounds like we're creating the tag alongside the release.

@@ -58,9 +63,9 @@ fi
# exit 1
# fi

if [ "$DOCKER_HUB_REPO" == "$PRODUCTION_DOCKER_HUB_REPO" ]
if IsProductionRelease
Copy link
Member

Choose a reason for hiding this comment

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

👌 ty for the fix

@brianluong brianluong merged commit 5afae6f into main Aug 30, 2022
@brianluong brianluong deleted the publish_github_tag branch August 30, 2022 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants