Hello, On Wed, Jul 27, 2016 at 1:52 PM, Sofia Tania <[email protected]> wrote:
> The pipeline isn't picking up the latest version of the > Acceptance-Test-Suite repo because "Poll for new changes" is not ticked. > With that not ticked, I believe the only time GoCD will actually fetch new > changes from Acceptance-Test-Suite repo is when that last pipeline is > triggered manually. If the pipeline runs automatically after the Deploy > pipeline has run, it won't fetch new changes from the Acceptance-Test-Suite > repo. > Sofia, your answer is spot on. I think your understanding is fine. :) > Conceptually > <https://docs.go.cd/16.4.0/introduction/concepts_in_go.html#materials>, a > material is a cause for a pipeline to run. What you want is for the > pipeline to be triggered (caused) by a deploy (previous pipeline), then to > fetch a new version of Acceptance-Test-Suite before the test is run. One > way I see you could achieve this is by *not* setting the > Acceptance-Test-Suite repo as a material, but instead, setting up a task to > do the git pull from master branch before you run the test. > Yes, that can be done too. Another option is to turn on polling and blacklist the material, as mentioned in this possibly relevant discussion <https://groups.google.com/d/topic/go-cd/1K_XXur-LIU/discussion>. Hope that helps, Aravind -- 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.
