Forum Discussion
Can't trigger a pipeline hosted in RepoA when a commit is pushed to RepoB
I’m using Version Dev17.M153.5 (TFS), and I have two repositories: my source code is hosted in Repo B, and my pipelines are hosted in Repo A to keep responsibilities separated. My goal is for the pi...
The main reason your pipeline isn't triggering is because of the version of Azure DevOps Server you're using. You're on TFS Version Dev17.M153.5, which corresponds to Azure DevOps Server 2019 Update 1. In this version, resource triggers for repositories aren't supported in YAML pipelines. This feature was actually introduced later, in Azure DevOps Server 2020.
To resolve the issue, you might consider:
1. Upgrading to Azure DevOps Server 2020 or later: This would allow you to use resource triggers in your YAML pipelines.
2. Moving your pipeline YAML file to Repo B: This way, commits pushed to Repo B would directly trigger the pipeline.
3. Setting up a service hook or using the REST API: As a workaround, you can trigger the pipeline from Repo B using these methods.
Hope this helps! Let me know if you have any questions or need more assistance.
To resolve the issue, you might consider:
1. Upgrading to Azure DevOps Server 2020 or later: This would allow you to use resource triggers in your YAML pipelines.
2. Moving your pipeline YAML file to Repo B: This way, commits pushed to Repo B would directly trigger the pipeline.
3. Setting up a service hook or using the REST API: As a workaround, you can trigger the pipeline from Repo B using these methods.
Hope this helps! Let me know if you have any questions or need more assistance.
