Environment UX overall issues

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

I'm doing my best to use gitlab environments but after weeks of work and reading the documentation I'm frustrated because in general the Environments web interface does not work properly on some cases and need improvements to made it useful.

I want to head informing that in many issues I found that more users are doing as I do, go to CI/CD pipelines, find the job for the deployed environment and run jobs from there.

Issues for Deployments / Environments

1. UX: The play button show the work defined to stop the environment and beside you show a big stop button that supposed to run that job.
   • Proposed solution: Do not show the on_stop job in the play button
   • Proposed extra: in the Pipelines view add the stop button and do the same.
2. UX: When I click in the stop show the message "Note that this action will stop the environment, but it will not have an effect on any existing deployment due to no “stop environment action” being defined in the .gitlab-ci.yml file." even if I have it defined in my pipeline. If I click in "Stop environment" it works. This was working properly months ago, probably a more that a year.
   • Proposed solution: Fix the check, if the on_stop is defined do not show this message.
3. If you click in stop and the stop the environment is not showed neither in Available or Stopped envs. Worst, if the stop job is not successful then even if the env still there (not stopped properly) is not showed.
   • Proposed action: add a Processing tab between Available and Stopped and show the envs running jobs in there
   • Proposed alternative: if you show the pipeline (proposed bellow) just show the env in Available because the pipeline will indicate that is doing something.
4. UX: Will be great if you do not redeploy jobs tagged as action:access (same for prepare and check) because while looking at the interface my understand is that the idea is to redeploy the environment itself.
5. UX: Idea: As most users are just using the pipelines to redeploy, stop and do other operations (shrot: re-run jobs) for for the environment could be good idea to show the pipeline circles in the environment job, this can made things easier and the usage consistent.