Address discrepancy between Web interface and docs re: "Skip outdated deployments
Summary
There is a slight discrepancy between the docs and the GitLab web interface where Skip outdated deployment jobs is concerned.
The Web interface says:
"When a deployment job is successful, skip older deployment jobs that are still pending."
Navigate to Settings > CI/CD and expand General pipelines to view Skip outdated deployment jobs. This is located in https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/views/projects/settings/ci_cd/_form.html.haml#L31.
The docs say:
"When enabled, any older deployments job are skipped when a new deployment starts."
The copy in the Web interface indicates that the impact of Skip outdated deployment jobs is limited to deployment jobs that are pending
. The docs suggest that the impact is not limited to pending
jobs.
📋 Next Steps
-
Complete issue -
Confirm -
Submit MR
🎫 Ticket Info
GitLab team members with access to ZenDesk can review the ticket
This change is somewhat similar to the one recently merged in !63795 (merged).
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
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`)
Results of GitLab application Check
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)