-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Publish the Helm chart tarball with each release #3849
Conversation
I took a look tonight, I'd rather we try to use the action I suggested in the other PR. That being said, your PR would not be working either because you also need to add the other helm repos for the build to work at least. Cheers and thanks for the feature idea :) |
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.
Needs at least helm repo add.
I think this is more flexible and can offer what we'd want, compared to my testing done through https://github.com/DefectDojo/django-DefectDojo/pull/3923/files If you could please make the suggested changes, I could test it further. Cheers! |
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.
I would think the last easy change :) Cheers.
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.
lgtm now, we'll see how it rolls and tune if needed :) Thank you!
Hi @bgoareguer, We are already using the gh-pages branch to publish our defectdojo documentation. I am not sure if it is a good idea to use this branch for publishing helm charts too. Can we use any other branch or is it not a problem? There is already a predefined github action for publishing helm charts: https://github.com/stefanprodan/helm-gh-pages. Is there a reason for maintaining our own action? |
Hi @alles-klar, I didn't know about https://github.com/stefanprodan/helm-gh-pages. I think it can be reused here. Github seems to allow only a single Github Pages site per Github project, so it is not possible to publish the Helm chart to a different branch. |
I didn't know either, good find @alles-klar
With the above action, it seems you can. Per their README:
|
Sorry if I was unclear. Yes, the above action lets you publish the chart to any branch, but the restriction is on Github side: you can only have a single Github Pages site per project. You already configured Github Pages to serve the DefectDojo documentation from the |
I think that hosting the Helm chart in a dedicated project would be the cleanest solution. |
I just did a test without gh-pages (after reading an article), seems to work. Checked out a new branch in my fork, packaged the last from
committed and pushed the resulting tgz and index.yaml file.
Search for defectdojo helm chart
Could that be a viable option? If so, we could just modify @bgoareguer 's method and just tweak it, and not reinvent any of any wheels. |
Idea of actual name for the official branch: |
I like the idea @madchap! Naming: Do we want to push more then the helm package to this branch? If not I suggest to name the branch "helm-charts" because the name doesn't have to contain "defectdojo" - it is already in the name of this repository. Reinvent the wheel: We can start with the solution from @bgoareguer but in the feature I prefer to the predefined action https://github.com/stefanprodan/helm-gh-pages. Less code to maintain and easier to read. |
But incompatible with our documentation. Let's start with that and see how it behaves for 1.14.0. I will make the small mods to the PR now. |
Ok, lets go. Anyhow, a short paragraph in the documentation would be nice! |
Yep, pinged you on the companion PR ;-) |
Fixes #3778
Pre-requisites:
gh-pages
as source branch and/ (root)
as the folderThe Helm chart tarball is published as a release asset.
The
gh-pages
branch is used to store the Helm repository index. Each version of the chart points to the asset added to the corresponding release.The resulting Helm repository should be added with the following command (not sure about the capital letters):