Hi, thanks for the response. Yes, I know about that option but it's not what I need. I still need to be able to run stage "deploy-to-test" for that Utility every commit to Mercurial since tests in App * could be depending *about it in the Test environment. It could be possible that my Test environment is broken without the latest code. How do you do it, what's your strategy/would be of deploying this kind of setup?
Kind regards, Matija On Thursday, November 24, 2016 at 9:13:58 AM UTC+1, Varsha Varadarajan wrote: > > Hello, > > You probably already know this. > One thing you could do is set up an upstream dependency in the Utility > pipeline as App pipeline run-tests stage. However, the drawback is that > even the first stage (deploy-to-test) of the Utility pipeline will not get > triggered until the run-stage of App pipeline completes. You could use this > if you are okay with the automatic trigger of deploy-to-test of Utility > pipeline being delayed. > > A material dependency can be set up for a pipeline and not a stage. > > Thanks, > Varsha > -- 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.
