A lock can only lock 1 pipeline. Dependent pipelines have nothing to do with the lock.
Marius On Thursday, June 9, 2016 at 2:25:22 AM UTC+1, Pankaj Lal wrote: > > Please refer to following documentation > > https://docs.go.cd/current/configuration/admin_lock_pipelines.html > > " > > Sometimes you want to ensure that only a single instance of a pipeline can > run at a time. This is important if the stages of a pipeline are > interrelated. For example the first stage may set up an environment that is > used by the next stage in the pipeline. > > If a pipeline is locked then Go will not allow any other instance of that > pipeline to be scheduled until the currently running one has been completed. > > " > > I want to know if locking pipeline would lock this pipeline if any other > downstream pipeline triggered by this pipeline is currently running. I > expect this to happen because first pipeline creates a deployment that is > then used by subsequent test pipeline. The two pipelines run in two > different environments but conceptually they are one set of serial > activities. They are in separate pipelines because they need to be > triggered from different kind of agents and hence different environments. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
