You are spot on. We do share one of the repositories for the all microservice(aka upstreams). And was able to simulate and see where the fan-in didn't happen when upstreams do not share any of the materials.
Thanks for prompt response, Mani On Tue, Jun 13, 2023 at 8:43 AM Chad Wilson <ch...@thoughtworks.com> wrote: > If it's "not monorepo", can you clarify if you have multiple upstreams > that point to one repository/material? That is the scenario that triggers > fan-in, and that does at least indicate that the repo is somewhat being > treated as a monorepo in the sense that you have multiple pipelines > directly dependent on that repository. > > Otherwise you might need to share more specific examples of pipelines, > dependencies and the materials they have, along with the behaviour you > observe vs. desire. > > To successfully trigger a downstream, all upstreams only need to pass (on > a given material version) if they share a material. If they *do not* > share 1 or more materials then the behaviour should be as you describe - > the downstream will trigger with the last successful version of each > upstream stage (no fan-in required). > > -Chad > > On Tue, Jun 13, 2023 at 11:01 AM Manikkumar K < > manikkuma...@thoughtworks.com> wrote: > >> Ours is not monorepo. Is there any other alternative? >> >> On Tue, Jun 13, 2023, 07:18 Chad Wilson <ch...@thoughtworks.com> wrote: >> >>> 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 a topic in the >>> Google Groups "go-cd" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/go-cd/VVTYzU5OhV4/unsubscribe. >>> To unsubscribe from this group and all its topics, 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 >>> <https://groups.google.com/d/msgid/go-cd/CAA1RwH-Pub%3DUtDr0QEc-yS5DoR3BbKbagC0Jk8rfSYFDbiXe5Q%40mail.gmail.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/CACfO_cKcqovDwHrmD0G_yBP1cCYJJT%2BMs5hxV9KeTKrQmuf-OQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/go-cd/CACfO_cKcqovDwHrmD0G_yBP1cCYJJT%2BMs5hxV9KeTKrQmuf-OQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "go-cd" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/go-cd/VVTYzU5OhV4/unsubscribe. > To unsubscribe from this group and all its topics, 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/CAA1RwH8n%2BOm%3D5L13B3srVAhNZAPnHdrPZKJMh2sC7ZQrCB%2BJBw%40mail.gmail.com > <https://groups.google.com/d/msgid/go-cd/CAA1RwH8n%2BOm%3D5L13B3srVAhNZAPnHdrPZKJMh2sC7ZQrCB%2BJBw%40mail.gmail.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/CACfO_c%2BrsZviV4sMiy6%2BnTquWqWi7L6AafDc3%2B5Z%2BbhCrihzjg%40mail.gmail.com.
