Is there a way to setup a pipeline so that it will only be triggered with 
one material update at a time?

We have a pipeline X that depends on several other pipelines, say A and B 
for the sake of example. 
We have setup X with A and B as materials:

A -----|
       |
       -->X
       |
B -----|

X needs pipeline locking to be enabled. It takes several minutes to run, so 
it's common to have updates pushed to both A and B in the meantime. So, on 
the next run, X will have as materials the new versions of A *and* B. But 
we wanted it to run first with the new version of A, then with the new 
version of B. Is it possible to setup go to have this behavior?

-- 
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.

Reply via email to