Cannot change environment scope of global CI/CD variables anymore
Summary
When creating a new group variable in Group Settings -> CI/CD -> Variables, it's not possible to set the environment scope anymore. It's greyed out:
This is very inconvenient, as it means creating the same vars for the same environments over and over in all subprojects. Also, this used to work just fine, as we already make extensive use of it.
Steps to reproduce
- Go to Group Settings -> CI/CD -> Variables
- Add Variable
- Try changing the environment scope
Example Project
Example only possible with Maintainer/Owner status.
What is the current bug behavior?
The Environment Scope is greyed out.
What is the expected correct behavior?
Let me change the environment scope and create environment wildcards.
Relevant logs and/or screenshots
see above
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
gitlab.com
Results of GitLab application Check
This happens on gitlab.com
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)