(feature request) add pipeline trigger, when rocketchat code is updated, to trigger a new 'dev' helm chart to be released

[lknite]

helm has an option: helm search repo name --devel

This shows development releases which are not expected to be perfect/stable.

Generally when a source code update occurs it triggers the application to build. If this is setup for rocketchat, then an additional step could be added to rebuild the helm chart with the docker image version of the latest rocketchat container. Also, if there is an umbrella helm chart, that could then be rebuilt also with the latest helm chart version specified.

Something like renovate or kargo could then update git with the latest helm chart.

Then, a tool like argocd would update the dev deployment using the latest version set in git.

Such a frequently built helm chart doesn't have to be released, actually releasing a helm chart could still be part of a release cycle.

All this is said just to suggest the idea of having the helm chart as part of the build deploy process, which would ensure its not forgotten.

[devadharshini-162]

Hi team 👋
I’ve gone through this issue and the proposed approach around triggering a dev Helm chart release on Rocket.Chat code updates. I’d like to work on implementing this end-to-end (CI trigger → Helm chart update → dev deployment).

If there are no objections, could you please assign this issue to me? Happy to align on the expected workflow before starting.

[PrashamJain1318]

Hi @lknite,

I'm interested in contributing to this feature request. This is a great idea for automating the helm chart release process whenever RocketChat code is updated.

I have experience with:

• CI/CD pipelines (GitHub Actions, GitLab CI)
• Helm charts and Kubernetes deployments
• Automation tools like Kargo and ArgoCD
• Docker image versioning and tagging

I understand the proposal is to:

1. Set up a pipeline trigger that watches for RocketChat code updates
2. Automatically build and push new docker images
3. Update the helm chart with the latest image version
4. Release the updated chart for the 'dev' environment
5. Optionally update umbrella helm charts

I would like to:

• Start by understanding the current deployment process and CI/CD setup
• Review existing GitHub Actions workflows in the RocketChat/Rocket.Chat repository
• Propose an implementation approach that integrates with the helm-charts repository
• Create a proof-of-concept for the dev release pipeline

Could you please assign this issue to me or let me know the next steps to get started?

Thank you!