Determine if Gitlab environments/deployments/resource_groups meet our needs for locking
As part of improving locking for the GitLab Kubernetes deployment process, we want to leverage the GitLab environments and deployments as well as resource groups to ensure that only one change is happening to an environment at one time.
In order to make sure we can conceivably use these features, we need to confirm that
-
We are able to ensure that for each environment we have defined, only one pipeline or set of jobs are able to run against that environment (jobs in different pipelines can't interleave) -
There is an API or way for us to manually lock and unlock an environment/resource group so we can have outside processes (such as auto-deploy) lock/unlock an environment -
Ideally we are able to ensure only one pipeline or set of jobs are deploying to an environment across all projects in a group -
UI to easily determine what pipeline or change is currently deploying to an environment (or locking a resource group) gitlab-org/gitlab#353369 gitlab-org/gitlab#342017 gitlab-org/gitlab#342016 (closed)
Edited by Graeme Gillies