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 github action to release tempto #286

Merged
merged 5 commits into from
Feb 12, 2025

Conversation

unidevel
Copy link
Contributor

@unidevel unidevel commented Jan 31, 2025

This PR is sitll in progress.

Testing action in this repo => https://github.com/unix280/tempto/actions/workflows/release.yml

Test passed with test GPG key and test maven repo => https://github.com/unix280/tempto/actions/runs/13102076676

Environment setup:

  1. In the repo settings-> Environment, create a new environment named release
  2. In the enviroment settings, check Required reviewers, and select reviewers
  3. Create the Environment secrets in the release environment settings
  • PRESTODB_CI_TOKEN - token of prestodb-ci to push the commits
  • GPG_SECRET - GPG private key
  • GPG_KEYID - GPG key ID
  • GPG_PASSPHRASE - GPG key passphrase
  • NEXUS_PASSWORD - Password for Nexus repository
  • NEXUS_USERNAME - Username for Nexus repository

@unidevel unidevel marked this pull request as ready for review February 2, 2025 20:15
Copy link
Contributor

@aaneja aaneja left a comment

Choose a reason for hiding this comment

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

LGTM

major=$(echo $release_version | cut -d. -f1)
minor=$(echo $release_version | cut -d. -f2)
# Increment the minor version
last_minor=$((minor - 1))
Copy link
Contributor

Choose a reason for hiding this comment

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

what happens here if minor == 0? e.g. assume we release a 2.0

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, seems I need a new parameter and flag for this, I'll update later.

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think you need to add a flag -- the likelihood that we ever end up releasing anything other than 0.x is low. However, I think it would be good to add a check and just error out here with a message saying that the pipeline doesn't handle a new major version

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated @ZacBlanco

@wanglinsong wanglinsong merged commit 6462ba8 into prestodb:master Feb 12, 2025
2 checks passed
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.

4 participants