Skip to content
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

Run package-kubeapps-version.sh automatically on bitnami chart release #14

Open
absoludity opened this issue Apr 19, 2022 · 3 comments
Open

Comments

@absoludity
Copy link
Contributor

The last step in the automation will be to run the carvel release automatically when the bitnami chart is released.

This is more of an infrastructure task, as it may need to run as part of the bitnami pipeline within the VPN.

@castelblanque
Copy link
Contributor

It would be nice having every step automated.
Are we sure that we want to mirror the releases to Bitnami chart?
If package is not to be included until the next TCE version, it might not be that necessary.

@absoludity
Copy link
Contributor Author

Yeah, it wouldn't need to be every bitnami chart release, perhaps just our Kubeapps releases, but note that running the script doesn't add the carvel package to TCE, it just generates, tests and publishes to the registry. We can still choose which versions get added to TCE.

@ppbaena
Copy link
Contributor

ppbaena commented Jun 24, 2022

Yeah, it wouldn't need to be every bitnami chart release, perhaps just our Kubeapps releases, but note that running the script doesn't add the carvel package to TCE, it just generates, tests and publishes to the registry. We can still choose which versions get added to TCE.

+1. So we have it automated and tested to decide which version get added to TCE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🗂 Backlog
Development

No branches or pull requests

3 participants