Manually stop an environment
Problem to solve
Environments are sometimes disposable and unlikely to be reused in the future. One clear example is Review Apps, where the environment is created new every time. At the moment, the only way to manually "stop" an environment is to use a proper pipeline job, but sometimes you want to stop an environment from the UI, in a specific moment.
Stopping an environment is also important to keep your environment list clean, since stopped environments are in a separate tab.
Design
Environment list
- Re-order buttons, so stop action is at the end
- Stop action button becomes primary (full red with white icon)
- Use the new icons from http://gitlab-org.gitlab.io/gitlab-svgs/ instead of FontAwesome
- Use
stop
icon for stopping of environment - Use
repeat
icon for re-deploy - Get rid of any s12 classes (icons should just be 16x16)
- Use
- New tooltips:
Open live environment
Re-deploy to environment
Stop environment
- Apply this to review environments as well
Environment detail view
- Make stop button also show up for normal environments
- Add stop icon to stop button (similar to buttons next to it)
- Change text only buttons to icon only buttons with tooltips
- Icons:
- Use
repeat
icon for re-deploy - Use
redo
icon for rollback
- Use
- Tooltips:
Re-deploy to environment
Rollback environment
- Icons:
- Make sure the rows line up example
- Default modal will be changed to a gitlab native modal.
- If no stopping action has been defined in the .gitlab-ci.yml you will be presented the modal with the warning
Copy:
Stopping Production?
Are you sure you want to stop this environment?
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.
Learn more about stopping environments
Miscellaneous
- Make sure https://gitlab.com/gitlab-org/gitlab-ce/issues/25388#note_56788671 is fixed
Edited by Dimitrie Hoekstra