-
Notifications
You must be signed in to change notification settings - Fork 23
Automate Kolla version updates #1532
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
Conversation
…ayobe-config into automate-version-pin
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.
Out of curiosity, did you consider using dependabot for this? https://docs.github.com/en/code-security/dependabot
I don't know if dependabot would work with our Kolla dependencies, I didn't dig into it too much anyway, this is following the Azimuth dependency update method https://github.com/azimuth-cloud/azimuth-config/blob/devel/.github/workflows/update-dependencies.yml |
Tested here Looks good! |
Hang on, is this going to trigger on every branch, every night? |
I think it's just the default branch: https://github.com/azimuth-cloud/azimuth-config/actions/workflows/update-dependencies.yml |
Hmm, so it won't be able to support multiple releases at once. We'll probably want to expand this out to a matrix job one Epoxy is out. This is fine for now though |
Think this is an ongoing issue for Github https://github.com/orgs/community/discussions/16107 |
Automated Kolla dependencies updates
/cherry-pick stackhpc/2023.1 |
Cherry-pick failed with |
Automated Kolla dependencies updates
PR tests:
This workflow will require enabling GitHub Actions pull requests (already enabled):
https://docs.github.com/en/[email protected]/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests