Doing that means removing the guarantees fan-in offers you as to consistency of the material versions on upstream pipelines when triggering a downstream.
It's possible to turn off fan-in globally (although I have never done so personally) but to my knowledge not for individual pipelines. Alternatively, if your upstreams are some sort of monorepo which are segregated by upstream pipelines (e.g each pipeline operates on different subdirectories or parts of the repo) you could consider using something like https://github.com/TWChennai/gocd-git-path-material-plugin to define separate materials for each of the upstreams that share a repo with different subsets of the repo that they operate on so GoCD doesn't decide they need fan-in. -Chad On Tue, 13 Jun 2023, 08:39 Manikkumar K, <manikkuma...@thoughtworks.com> wrote: > We do have a fan-in where number upstream has exploded in the count, > > Instead of waiting for all upstream to pass, can we pick most recent > successful upstream pipeline along with new pipeline instance of one(or > more) of upstream? > > Thanks, > Mani > > -- > 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 go-cd+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/go-cd/4bcad889-0820-427b-ac85-d91e50f24e43n%40googlegroups.com > <https://groups.google.com/d/msgid/go-cd/4bcad889-0820-427b-ac85-d91e50f24e43n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 go-cd+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAA1RwH-Pub%3DUtDr0QEc-yS5DoR3BbKbagC0Jk8rfSYFDbiXe5Q%40mail.gmail.com.
