environment: action: access and action: verify Do Not Reset environment: auto_stop_in timer
Summary
Jobs with environment.action: access|verify
do not reset the auto_stop_in
timer for the environment.
Steps to reproduce
- Create a job which creates an environment and sets a
auto_stop_in
:
environment:
name: my-environment
auto_stop_in: 1 hour
- Create another job which access that environment using the
action: access
oraction: verify
options:
environment:
name: my-environment
action: access
What is the current behavior?
When the job with environment.action: access|verify
runs, the auto_stop_in
timer is not reset/suspended.
Currently the timer resets only for environment.action: start
. It should reset for access|verify
as well.
What is the expected behavior?
Accessing the environment should reset the auto_stop_in
timer just like the job which creates the environment does on subsequent runs.
Release notes
GitLab can automatically schedule an environment to stop after a configured period of time. Until now, the environment's lifetime was updated only if the environment was updated through a job with environment.action: start
(the default value). As environment.action: access
and environment.action: verify
actions both assume that the environment is still running, we are enhancing the environment auto feature to reset its timer when access
or verify
jobs access the environment.