I think my reply on https://groups.google.com/g/go-cd/c/iKaEfamf3gM/m/9BcLnhQxBAAJ is relevant here - assuming you are using the build status plugin <https://github.com/gocd-contrib/gocd-build-status-notifier>, if the downstream repos (e.g functional tests) don't have a direct link to a commit belonging to a PR via a direct material, I don't think there is a way for GoCD to report the status - i.e I don't believe it can "walk the VSM" back to the originating materials that are part of this build run to figure out which PR was responsible for the run.
You might be able to extend the plugin though; I haven't thought about what is technically possible or not. -Chad On Sun, Jun 19, 2022 at 1:05 AM 'Ehtesham Kafeel' via go-cd < [email protected]> wrote: > We have a feature that is based on different micro-services all having > their own Github repository. We run our functional tests as a downstream > pipeline so that we can run it if there is a change in any of the upstream > micro-service. If we add it to stage then we will have to add that stage to > every main pipeline. The functional tests downstream pipeline has a git > material from where it checks out the test code. > On Saturday, June 18, 2022 at 3:05:12 PM UTC+4 [email protected] wrote: > >> On Sat, 18 Jun 2022 at 3:43 PM, 'Ehtesham Kafeel' via go-cd < >> [email protected]> wrote: >> >>> Hi, >>> >>> We run our functional tests as downstream pipeline that runs on >>> completion of multiple upstream pipelines with git as material, a GitHub Pr >>> to be precise. We obviously get the status checks on the PR for the >>> upstream pipeline but we also want to report the status of the downstream >>> pipeline to the PR as status check. >>> >>> Can we accomplish this with just GoCD? >>> >>> Could you combine the upstream and the downstream pipeline? >> >> We sometimes find users keeping stages in separate pipelines, whereas >> those stages are better kept together within a single pipeline. >> >> In your case, if the first pipeline runs some checks in a stage and the >> next pipeline runs further checks, then you may want to review whether >> keeping all the stages together is appropriate. >> >> >> -- >>> 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/05696206-e7b1-47a4-84cf-b4cc4c7d5b18n%40googlegroups.com >>> <https://groups.google.com/d/msgid/go-cd/05696206-e7b1-47a4-84cf-b4cc4c7d5b18n%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/0cf16073-2bcf-4458-a4bf-f9a02d178475n%40googlegroups.com > <https://groups.google.com/d/msgid/go-cd/0cf16073-2bcf-4458-a4bf-f9a02d178475n%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-MOYRZ8%2BtRS%2Byo%3D3_Hu35Rwjaf4kD45%3DZumHBFvZBQRg%40mail.gmail.com.
