CI/CD workflow to publish helm chart #450
Conversation
|
Hi @robinson, thanks a lot for your PR ! But as you can see, it doesn't pass the DCO requirements. Could you please sign/verify and sign off your commits ? |
Signed-off-by: lth <[email protected]>
cdavernas
added
priority: low
cdavernas
added
type: enhancement
deployments/helm/Chart.yaml
Outdated
| version: 1.0.0-alpha5.1 |
There was a problem hiding this comment.
Will we have to update this manually upon every release? If so, isn't there a way to automatize it using the CI pipeline?
There was a problem hiding this comment.
let me making a test it with auto version based on the release.
There was a problem hiding this comment.
looks like not trivial :-) the most popular helm release strategey should be 1-1 versioning, that means, when new release taking place, simply creating a new version helm chart folder (refer: https://codefresh.io/docs/docs/ci-cd-guides/helm-best-practices/#simple-1-1-versioning) what do you think?
|
Btw, should this PR be merged in main or in gh-pages ? |
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
Signed-off-by: lth <[email protected]>
the gh-pages branch use to create a pages in order to publish the artifacts. The helm release workflow should be run in main branch. |
Many thanks for submitting your Pull Request ❤️!
What this PR does / why we need it: CI/CD flow to publish helm chart
Special notes for reviewers: need another step to publish into https://artifacthub.io/
Additional information (if needed):