'Deploy to' label on environment is not necessarily right

Closed: duplicate

This issue is closed in favor of #375235 (closed)

Summary

Under Operations > Environments > Environment the 'play' button says Deploy to... for all manual jobs in .gitlab-ci.yml.

In case of review apps we generally stop them to clean up the old environment. We're not deploying anything at that time.

CI / CD > Pipelines has Manual job as its label. Which doesn't do anything (a bit weird from a UX perspective) but it is a better label.

Steps to reproduce

(How one can reproduce the issue - this is very important)

Example Project

https://gitlab.com/gitlab-org/gitlab

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

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)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited Sep 29, 2022 by Andrei Zubov