Thats weird. Do you have a pipeline dependency setup for the pipelines. What I mean is - BuildSS downstream pipeline with BuildCommons pipeline as a pipeline material. https://docs.gocd.io/current/configuration/managing_dependencies.html
I quickly setup below scenario and it worked as expected. Downstream pipeline only get triggered once the upstream is finished and have the latest commits of github material. [image: Inline image 1] On Thu, Apr 13, 2017 at 2:31 PM, Diogo Oliveira <[email protected]> wrote: > Hi, > > Thanks for your answer :-) > > The problem is that I've done some experiments and I'm actually not > observing that... What is happening is that when I commit on both /Commons > and /SS both pipelines are being scheduled at the same time, the second one > with the previous /Commons version :-( > > quinta-feira, 13 de Abril de 2017 às 07:02:14 UTC+1, Ankit escreveu: >> >> Hi Diogo, >> >> >> My question now is: if I make a commit that changes files on both >> /Commons and /SS, since BuildSS depends on BuildCommons and they share the >> /Commons material, I was expecting that the BuildSS pipeline would only >> schedule when the first finished. >> >> Your understanding is correct. BuildSS will only get triggered once >> BuildCommons is finished. You can read more here about the pipeline >> dependencies: https://docs.gocd.io/current/configuration/man >> aging_dependencies.html >> >> As there was change in both /Commons and /SS, BuildSS will wait until >> BuildCommons >> finishes as per above. Later once BuildCommons is build successfully, >> BuildSS will get triggered with latest commits of /Commons, /SS and >> whatever the state of /Plugins material. >> >> Cheers, >> Ankit >> >> On Tue, Apr 11, 2017 at 9:08 PM, Diogo Oliveira <[email protected]> >> wrote: >> >>> Hi guys, >>> >>> I was trying to model something in Go and some questions arised in the >>> way that go manages dependencies and pipeline scheduling. Namely, I'd like >>> to know if the behavior I'm observing is the expected. >>> >>> So, what am I trying to do? >>> >>> I have one pipeline that depends on a previous pipeline. Both share a >>> common material, but the second one has more materials that are not on the >>> first pipeline. A relevant detail is that all the materials are subfolders >>> of the same SVN branch, so I can actually commit in more than one >>> "material" at the same time. >>> >>> Let's look at a small picture to make the problem understanding easier: >>> >>> >>> <https://lh3.googleusercontent.com/-J0Q8AzBD0zo/WOz39hxBXzI/AAAAAAAAGM4/t_Kr2B_ET0k_dVzw9yyB24GaIG1-1xZDwCLcB/s1600/godeps.PNG> >>> >>> >>> So, this is the setup. >>> >>> >>> My question now is: if I make a commit that changes files on both >>> /Commons and /SS, since BuildSS depends on BuildCommons and they share the >>> /Commons material, I was expecting that the BuildSS pipeline would only >>> schedule when the first finished. >>> >>> >>> On the other hand, I also committed on /SS, so I understand that BuildSS >>> pipeline detects that it has material changes that are not shared by >>> ancestor pipelines. >>> >>> >>> So, my question is: what is the expected behavior here? :) >>> >>> >>> Thanks in advance! >>> >>> >>> Best Regards, >>> >>> Diogo Oliveira >>> >>> -- >>> 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. >>> >> >> -- > 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. > -- 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.
