<https://www.go.cd/assets/images/image10.png>
<https://www.go.cd/assets/images/image09.png> If triggering a pipeline requires *ALL* of its upstreams to be successful (and not just ANY ONE), does it mean that Capacity Testing Pipeline (which shows that it has 2 upstreams - the BuildPipeline and the SVN Material) will be triggered only if Build Pipeline is successful and ALSO there is a new commit in SVN material? It means, the completion of Build Pipeline will successfully trigger the User Acceptance Pipeline but it will not trigger the Capacity Testing Pipeline because the Capacity Testing Pipeline must ALSO wait for a new commit in SVN material. Is that correct? On Thursday, September 8, 2016 at 12:20:50 PM UTC+6, Aravind SV wrote: > > On Thu, Sep 8, 2016 at 11:37 AM, Syed Rakib Al Hasan < > syed.raki...@gmail.com <javascript:>> wrote: > >> Yes. That would be me and @Tomzo. However, a few matters remained unclear >> in the brief discussion. Also, it's kind of difficult to keep focus on one >> topic in a gitter chat since there are so many discussions happening in a >> single thread. Hence, wanted to ask the question separately over here with >> a dedicated thread. >> > > Makes sense. I replied to the other mail of yours (with the subject "VSM > vs MultiStage/MultiJob design") and my response from there goes for this as > well. > >> does having multiple upstreams to a single pipeline require *ALL* of its >> upstreams to complete successfully to trigger the pipeline? Or will the >> pipeline be triggered by *ANY ONE* of the upstreams being successfully >> completed? > > > For a downstream pipeline, it needs successful upstreams for it to > trigger. All of them. > -- 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 go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
