Skip to content

Environment Auto-Stop: Feature to Adjust Expiry Time and Remove "Pin" Option

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

Release notes

Add ability to extend an auto-stop environment stop time.

Problem to solve

Using the auto-stop feature of a gitlab environment, I can provide a single expiry time when the environment is created. In many situations, this expiry time is sufficient, but there are many other situations where the user needs an environment for more time. Currently, the only option is to remove the expiry time altogether ("pin" the environment). The problem is that once an environment is pinned, it will never go away on it's own. Most times, users want an extra day or two, not "forever", and then they end up forgetting about the env, which costs us money.

Intended users

Intended for users of time-limited GitLab Environments:

User experience goal

A user creates an environment, and upon realizing they require the environment to survive longer than the prescribed (auto-stop) time limit, they are able to extend the lifetime of the environment by clicking some buttons in the gitlab web UI.

Proposal

The enhancements I'd like to see would be to: A) Enable users to delay the auto-stop job, rather than disable it altogether. This could be in the form of, say, some "+", "-" buttons to add or remove one hour at a time.
B) With the option to extend an environments "stop" job delay, the "pin" option should be removed. An "auto stop" job would ideally have a flag - either "pin" or "extend" (I suppose the general case would be to provide one or the other or both - in my case, I wouldn't want to have both).

Edited by 🤖 GitLab Bot 🤖