[CI] Make the API diff be triggered as soon as the config of the build is done.#21880
[CI] Make the API diff be triggered as soon as the config of the build is done.#21880mandel-macaque merged 1 commit intomainfrom
Conversation
…d is done. The allows the pipeline to be triggered by the build allowing use to not need to tell azp to run apidiff and simply use '/azp run xamarin-macios-pr'
|
/azp run xamarin-macios-pr |
|
we should see the api diff comment without triggering the pipeline |
|
Azure Pipelines successfully started running 1 pipeline(s). |
✅ [CI Build] Build passed (Build packages) ✅Pipeline on Agent |
🔥 [CI Build] Build failed (Build macOS tests) 🔥Build failed for the job 'Build macOS tests' (with job status 'Canceled') Pipeline on Agent |
🚀 [CI Build] Test results 🚀Test results✅ All tests passed on VSTS: test results. 🎉 All 107 tests passed 🎉 Tests counts✅ cecil: All 1 tests passed. Html Report (VSDrops) Download Pipeline on Agent |
Unfortunately Azure DevOps doesn't properly report GitHub checks for pipelines triggered by another pipeline, when that other pipeline was triggered from a pr trigger. So go back to triggering the API diff pipeline using a pr: trigger. This effectively reverts #21880 ("[CI] Make the API diff be triggered as soon as the config of the build is done.") References: * https://stackoverflow.com/questions/78443654/reporting-stage-statuses-to-github-for-pipeline-triggered-by-another-pipeline
Unfortunately Azure DevOps doesn't properly report GitHub checks for pipelines triggered by another pipeline, when that other pipeline was triggered from a pr trigger. So go back to triggering the API diff pipeline using a pr: trigger. This effectively reverts #21880 ("[CI] Make the API diff be triggered as soon as the config of the build is done.") References: * https://stackoverflow.com/questions/78443654/reporting-stage-statuses-to-github-for-pipeline-triggered-by-another-pipeline
Unfortunately Azure DevOps doesn't properly report GitHub checks for pipelines triggered by another pipeline, when that other pipeline was triggered from a pr trigger. So go back to triggering the API diff pipeline using a pr: trigger. This effectively reverts #21880 ("[CI] Make the API diff be triggered as soon as the config of the build is done.") References: * https://stackoverflow.com/questions/78443654/reporting-stage-statuses-to-github-for-pipeline-triggered-by-another-pipeline
2 participants
This allows the pipeline to be triggered by the build allowing us to not need to tell azp to run apidiff and simply use '/azp run xamarin-macios-pr'