-
Notifications
You must be signed in to change notification settings - Fork 891
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
Jenkins Helm chart is now also published to GitHub packages registry (oci://ghcr.io/jenkinsci/helm-charts/jenkins) #1196
Conversation
72f33fd
to
989e6a2
Compare
Fixed the |
989e6a2
to
fb88f96
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets give it a whirl, can you make some sort of change to the chart as well please to trigger a release?
@timja Well I've just bumped the version which should be enough to trigger a release on merge |
- name: Install Helm | ||
uses: azure/setup-helm@v4 | ||
with: | ||
version: v3.12.0 | ||
version: v3.16.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This deserve perhaps renovate (on an other PR) to keep the binary up to date
Looks good: Perhaps the package view can be enabled for the repo (Like the deployments) |
done |
What does this PR do?
Publish also the chart to the GHCR registry
#1180
Submitter checklist
Special notes for your reviewer
This was inspired from https://github.com/fluxcd-community/helm-charts/pull/94/files
Chart is published on both location (the traditional GH page and the GH package)
I've tested the workflow change on my fork
https://github.com/jonesbusy/helm-charts/actions/runs/10828217018