Persist environment variables with pipeline
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
The environment variables state is not saved when a pipeline is run, so if we want to re-run jobs in a pipeline in the same state that it was run previously (i.e. roll back to a previous successful deployment) we would need to trigger a new pipeline and manually override all of the environment variables with their values at the time the pipeline was previously run.
Target audience
-
Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha
-
Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
Further details
Easy roll back to a previous successful pipeline.
Proposal
Persist the state of the environment variables along with each pipeline and when a job is run again it uses the same environment variables that it had the last time.
What does success look like, and how can we measure that?
The environment variables retain their state across job runs in a pipeline and do not take the latest version.