Expose reason for not creating the on_stop job on stopping the environment
Proposal
If certain conditions are not met, the on_stop
jobs will not be created. Currently, GitLab does not show the reason why such jobs were not created.
It'd be awesome if GitLab exposes the reason why on_stop
jobs are not triggered. It should save a lot of time trying to figure out what happened by trial and error.
Example: While working on this zd ticket(internal
), we figured on_stop
jobs wouldn't run if the environment is already stopped. If the reason/error message was exposed to the user, they could have easily understood the problem and fixed it.
Investigation issue: https://gitlab.com/gitlab-com/ops-sub-department/section-ops-request-for-help/-/issues/104 (internal
).