Changing group variable should rebuild/redeploy all projects
I've got a group, https://gitlab.com/demo-clusters, with several projects that all do the same thing, they use the stored configuration to update demo clusters. I could easily imaging having a group variable with the GitLab version number, and changing that one variable to automatically roll out changes to all of the affected clusters.
We don't currently trigger any CI/CD when variables are changed, but there's some good reason to do so. If we did, then changing a group variable could trigger rebuilds of tons of projects, which is great, and at the heart of release automation and configuration management (configuration as code).
I imagine we wouldn't want this to be default behavior (although Heroku does and it's fine). Perhaps we need to explicitly declare what variables a job depends on, or declare the "type" of variable (config time, run time, pass through to k8s, etc.).
Links / references
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Who is this for? Provide one or more use cases.
Make sure these are completed before closing the issue, with a link to the relevant commit.