You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document the process of making a package release include the use of release-drafter Github action to automate creation of a release and helm-releaser to publish the chart
#88
Open
devraj opened this issue
Oct 28, 2023
· 0 comments
Is your feature request related to a problem? Please describe.
With Github actions we should be able to automate the build and creation of releases. We already have many Taskfile based automations that build and publish our releases, we should move them to be triggered on Github via actions on specific events like a tag is published.
Describe the solution you'd like
I would like to see the following automation:
A person who has access to write to the default branch, publishes a tag
Github actions are triggered to runs tests
On success a container package is built and sent to GHCR
On success a helm chart is published on GHCR
At a later stage we can look at Terraform deploying the new image to the infrastructure.
For the initial solution we need Github actions for:
Running tests on the project
Building and publishing the container image on GHCR
Building and publishing the helm chart on GHCR
Create a draft release and possibly populate the release notes (partially anyway)
Is your feature request related to a problem? Please describe.
With Github actions we should be able to automate the build and creation of releases. We already have many Taskfile based automations that build and publish our releases, we should move them to be triggered on Github via actions on specific events like a tag is published.
Describe the solution you'd like
I would like to see the following automation:
For the initial solution we need Github actions for:
Describe alternatives you've considered
NA
Additional context
See:
release-drafter
chart-releaser
taskfile
The text was updated successfully, but these errors were encountered: