Thanks for the tip Varsha. I was able to resolve the problem. 1. I have to add `Deploy_Orchestrator_CI` as a dependency to `Deploy_Orchestrator_Pre_Prod`.
2. Even after this, I had issues of multiple deployments whenever there was a new material available in `git-repo1 or git-repo2 or git-repo3`. I have to add ignore patters on all the Service tests pipelines to ignore the material changes from git. Here is the updated VSM of `Deploy_Orchestrator_Pre_Prod` <https://lh3.googleusercontent.com/-c1dn7W2d1uk/WlY6HOha5TI/AAAAAAAAAQI/MUOw6-TCfUsWEH7u2h3XixO64qkBHoF2gCLcBGAs/s1600/Screen%2BShot%2B2018-01-10%2Bat%2B5.02.30%2BPM.png> Thanks Ketan and Varsha for the comments. - Prasanna On Wednesday, January 10, 2018 at 5:03:34 AM UTC+1, Varsha Varadarajan wrote: > > Hi, > > From the attached screenshot, it looks like fan-in is not setup at all. As > per the docs <https://docs.gocd.org/current/advanced_usage/fan_in.html> > - Fan-in material resolution will ensure that a pipeline triggers only when > all its upstream pipelines have triggered off the *same version of an > ancestor pipeline* or material. You can have the functional tests in > different git repositories. If you want fan in to kick in for > `Deploy_Orchestrator_Pre_Prod`, then the ancestor pipeline > `Deploy_Orchestrator_CI` must be made the upstream material for > `Deploy_Orchestrator_Pre_Prod` also. So, fan-in resolution will happen only > when the `Deploy_Orchestrator_Pre_Prod` and the functional tests pipeline > have a common material (be it a scm or a pipeline dependency) and for a > specific revision (git sha or pipeline build), all three functional tests > pipelines run first and then for the same revision, > `Deploy_Orchestrator_Pre_Prod` will run. > > Thanks, > Varsha > > On Wednesday, 10 January 2018 02:56:45 UTC+5:30, Prasanna wrote: >> >> >> Hi, >> >> I was referring this doc for fan-in >> <https://docs.gocd.org/current/advanced_usage/fan_in.html> configuration >> of GoCD to set up something like the image shown below. >> >> >> >> <https://lh3.googleusercontent.com/-kMQN5GTZBbQ/WlUx-aHoVBI/AAAAAAAAAPo/RSUDZmmLQbsixmRJUt9IOXjSS5_tkBtDACLcBGAs/s1600/Screen%2BShot%2B2018-01-09%2Bat%2B10.18.39%2BPM.png> >> >> >> I was expecting that "Deploy_Orchestrator_Pre_Prod" to be called once >> after all the 3 functional tests run successfully. However, each successful >> runs of the functional tests are triggering a deployment. >> >> So, if one of the functional tests fails, still the deployment happens >> twice. >> >> >> One thing that may be an issue here is that all 3 functional tests >> pipelines have their own git repository. Is it the case? How can I go about >> resolving this? >> >> >> I would like to deploy only after all 3 build is green. Let me know if >> you need further details. >> >> >> Thank you, >> >> Prasanna >> >> >> >> >> -- 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.
