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

Added support for PRs in chartReleaser workflow #42

Merged
merged 15 commits into from
Jul 16, 2024

Conversation

mhaswell-bcgov
Copy link

@mhaswell-bcgov mhaswell-bcgov commented Jul 15, 2024

  • PRs automatically trigger temporary charts to be released using the current Chart.yaml version (eg. this PR automatically released a 5.1.2-pr42 chart). The workflow only runs automatically if files inside helm/ are changed
  • The manual workflow run input no longer requires the user to input the entire chart version. It automatically takes the version from the Chart.yaml and appends the user input to it to create the tag. Because of this, we can no longer overwrite a release chart (eg. 5.1.2 with no hyphen) as the input won't allow it.
  • It's still possible to overwrite a release chart by creating a GH Release and not updating the version in Chart.yaml to match the release tag.

@mhaswell-bcgov mhaswell-bcgov marked this pull request as ready for review July 16, 2024 16:04
Copy link

@robrien-bcgov robrien-bcgov left a comment

Choose a reason for hiding this comment

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

fancy scripting stuff!

workflow_dispatch:
inputs:
chart_version:
description: 'The chart version to create. Must be a valid semver string and should indicate that it is not a release chart version (eg. 5.1.2-pr36).'
description: 'The chart version to create. Will be appended to the current version from helm/Chart.yaml (eg. "pr36" on Chart.yaml version: 5.1.2 produces "5.1.2-pr36").'

Choose a reason for hiding this comment

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

This isn't the most clearly worded (although the example is very useful). This is a sub-version or suffix essentially, right?

Copy link
Author

Choose a reason for hiding this comment

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

Yeah reading it back it wasn't very clear. How does this one read?

@mhaswell-bcgov mhaswell-bcgov merged commit 9152b83 into v5 Jul 16, 2024
3 checks passed
@mhaswell-bcgov mhaswell-bcgov deleted the feature/DESCW-2468-pr-chart-release branch July 16, 2024 21:57
mhaswell-bcgov added a commit that referenced this pull request Jul 26, 2024
* Added support for PRs in chartReleaser workflow
* Added path to image build to avoid rebuilding image when src hasn't changed
* Improved wording of workflow input description
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.

3 participants