I want to stop any pipeline from executing until the previous one has finished for a particular tag.
For example, I have a dev runner and a prod runner, each taking care of dev test deployments and prod deployments.
I am already using limits but they dont work. They prevent concurrency (two jobs running at the same time), but they dont necesarily prevent two interleaved piplines from occuring on the same runner which totally messes with my deployment workflow that requirs singular resources.
eg dev pipeline 1 may be up to job 7/10 for that pipe, and dev pipeline 2 may start at some point when I really dont want that happening. same for a deployment in production. its a singular resource, and once a pipeline starts it should own that resource until succesful completion or failure. Definitely not allowing another pipe to jump in there and start over.
Here is a link to a dead ticket where amyn others put effort into this - https://gitlab.com/gitlab-org/gitlab-foss/-/issues/20481
Like other issues I seem to find became a dead end for the gitlab-ce merge to gitlabb FOSS, and its been pretty frustrating in picking gitlab up. Most google results for any of my IAC question results in a dead end for me - almost everything I google terminates with the depressing
Hey! 👋 GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase.
So what happenned to all the people that took the time to communicate and work on this problem int hat thread? Is it just gone? its not clear if there is a solution. Most issues seem to commonly have threads that were started 3 years ago, and still aren’t resolved today.
Thanks if anyone can shed some light on all this, I’d like to get gitlab to work for me.