Make "release/deploy" easy and "destroy" difficult

Release notes

Problem to solve

As a Release Manager, I want to start a deploy job from the environments page and I don't want to miss it, so that I don't make a disaster.

Today, if a pipeline has two manual jobs:

  • deploy without special marks or marked with environment.action or environment.deployment_tier
  • destroy marked with environment.on_stop

The destroy job is a big, red button, while the deploy job shows up under a small button in a pop-up beside the destroy job. Very likely, the most important action would be to deploy, not to destroy

Following a customer call: https://gitlab.com/gitlab-com/user-interviews/-/issues/23#note_895935264

Proposal

  • Make the less visible
  • Make the deploy job more visible following some logic (any job that is not on_stop?)

Intended users

Feature Usage Metrics

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by Viktor Nagy (GitLab)