I could really use some guidance on whether this is an issue or if I need to change how my pipeline uses materials/artifacts so that a change in any one component will trigger the downstream pipeline.
Thanks! On Wed, Oct 11, 2017 at 9:12 AM, Jeff <[email protected]> wrote: > I'm working with five (5) Java WAR files, each deployed to their own > server (vm) for Functional Testing using 5 different pipelines. These 5 > pipelines then feed a single integration testing pipeline where all 5 WAR > files are deployed to two VM's in a 2 node cluster. > > It seems though that the integration testing pipeline is not automatically > scheduled unless all 5 applications are rebuilt. If only one is rebuilt, > the integration pipeline must be manually triggered. > > After manually scheduling it, it displays a warning that it was built from > incompatible revisions and appears to be complaining about a Git repository > we use to hold our Test Automation code. This same GIT repo is used for > both functional testing code in the 5 upstream pipelines as well as the > integration tests in the downstream pipeline that all others fan into. > > I don't know why the integration pipeline cares about what revision of the > test automation repository is used for the upstream functional pipelines > because it is NOT a material that is published. > > Is this expected? > > I could sure use some help understanding what is going on. > > Thanks! > > [image: Inline image 1] > -- 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.
