DEV Community

Discussion on: Multiple Repositories in a Single Azure Pipeline

Collapse
 
evan_noronha_701680e94280 profile image
Evan Noronha

It is also good if you keep your YAML file in a separate repository from the application code and you want to trigger the pipeline every time an update is pushed to the application repository.

hey dude! I separated my yaml from my main source repo for this exact reason. But now, my source repo doesn’t seem to get build statuses attached to commits—only the yaml repo does. Have you encountered this? Do you know of a solution?

Collapse
 
n3wt0n profile image
Davide 'CoderDave' Benvegnù

That's actually a good point... Let me see if there is a workaround for that.

Collapse
 
mohdemraan profile image
Mohammad Imran

Hey, were you able to find a solution for this? Do you also know what the "Related" column is for in the Sources pane on a run page of yaml based pipeline. I tried to search whole documentation but couldn't find any reference. I just shows "none" for the repo in which I keep the yaml file but nothing other application code repo. Don't know if this can be helpful somehow.

Thread Thread
 
n3wt0n profile image
Davide 'CoderDave' Benvegnù

No, I wasn't able to find any workaround. I also asked directly to the Azure DevOps product group and other MVPs but got no answers :(

On the "Related" it spells out Work-items and Artifact.
Work items will summarize the work items that are contained in the "build". How? It will analyze the commits you are builing and check the linked work items for those commits

Artifacts, instead, will summarize any build or pipeline artifact you publish in that pipeline

Thread Thread
 
andrewjw1995 profile image
Andrew Williamson

You can add a YAML file in your main source repository which extends from a template in your shared repository