Add first-class support for build version matrixes (especially Node) #24817
Replies: 2 comments
-
Would love to have this for GitLab's My use case is that I have jobs of the form test:
parallel:
matrix:
- K3S_VERSION:
- v1.20.15-k3s1
- v1.21.10-k3s1
- v1.22.7-k3s1
- v1.23.4-k3s1
services:
- name: registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/$K3S_VERSION
alias: k3s
# ... and I want I can imagine this working as a combination of two more general features:
|
Beta Was this translation helpful? Give feedback.
-
I know this is quite an old issue, but have ran into a similar usecase. I have a GH actions workflow with a build matrix that tracks release tags from another repo, so I have something like this:
It looks like I am able to able to obtain the latest release for "lolminer" with the "github-releases" data source template, however, I'm not sure how to have renovate append this latest release to the list of "lolminer" versions in the build matrix. |
Beta Was this translation helpful? Give feedback.
-
What would you like Renovate to be able to do?
Support build matrixes in a non-hacky manner.
Did you already have any implementation ideas?
Travis support previously had this but in a hacky approach which needed removing. We need to think of a better way which can co-exist with our regular updating approach.
Beta Was this translation helpful? Give feedback.
All reactions