Hi guys, I was trying to achieve a fan in behavior while using SVN externals, but the behavior I observed is either a limitation or I'm doing something wrong.
So, let me first tell you about my test scenario setup: SVN Branch SVN1: SVN branch which only contains externals inside it (to other folders in other branches); SVN Branch SVN2: SVN branch which only contains externals inside it (to other folders in other branches); Pipeline P1: pipeline that has SVN1 as a material; Pipeline P2: pipeline that has SVN2 as a material; Pipeline PFanIn: pipeline that has P1 and P2 as materials, plus SVN1 and SVN2. Now, one more relevant detail: both SVN1 and SVN2 have an external to the same place. So, I committed on that place. What was I expecting? --> Pipeline P1 and P2 would trigger with SVN1 and SVN2 revision after my commit, P3 would wait for P1 and P2 to finish and then trigger. What am I observing? --> Pipelnes P1, P2, and P3 are all triggered at the same time with SVN1 and SVN2 revision after my commit, ignoring the dependency to ancestor pipelines. Is this an expected behavior? Shouldn't fan in work with externals as well? Thanks in advance. Best Regards, Diogo -- 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.
