I think this is possibly a misunderstanding of the purpose of fan-in and pipeline/Value Stream design.
In the diagram you shared, the intent is to take the sum/aggregation of the outputs from the 3 source code repos, and 4 builds and produce a single package, while ensuring that the "package" pipeline is triggered by pipeline runs of build 2/build 3/acc 2/acc 3 based on *the same revision of source code from the middle source code repository*. If you want a single "package" pipeline, from a modelling perspective it would be expected every run to package all of the upstream "things" that are triggering it each time it runs, not just the trigger source, and thus to fetch the artifact independently for all upstream pipelines it is dependent on. If you have independent pipelines producing their own artifacts/products, you generally are not trying to do "fan-in" even if you want them to be deployed the same way. Generally you would want independent `deploy` pipelines, or stages that are part of other independent pipelines and to use approaches such as pipeline templates or pipelines-as-code to reduce duplication. That way every time such a "package" pipeline or stage runs it is clear in the visualisation exactly what is being packaged, rather than the action/result varying based on the upstream trigger source. This might be conceptually different to what you might be used to in some other build/deploy automation. -Chad On Sat, Feb 25, 2023 at 2:48 PM Xavier Quick <[email protected]> wrote: > like below picture, BUILD1, BUILD4 and Package, The Package pipeline don't > know which upstream pipeline triggered it, and how to get correct artifact。 > [image: image.png] > > 在2023年2月24日星期五 UTC+8 16:10:20<Xavier Quick> 写道： > >> I have more then one products, and created build pipeline for each >> product(material). After build ok, will upload artifact. And I just have a >> package pipeline for all products, it will be triggered whill any of >> previous build pipelines successed. But I don't know how the package >> pipeline fetch the artifact! For package pipeline, it regardless of which >> upsteam trigger it, just fetch artifact, pack them and upload installer. >> Are there any recommendations? > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/go-cd/b4824314-7576-4e4a-a292-6c96af16ecc3n%40googlegroups.com > <https://groups.google.com/d/msgid/go-cd/b4824314-7576-4e4a-a292-6c96af16ecc3n%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAA1RwH-9CZCXB8hh8%3DJ3FqAmj5dz4CMEa-vH94zAktjB61QUFQ%40mail.gmail.com.
