Enable post back of JIT test pipeline results to triggering GitHub PR #93138
Comments
BruceForstall
added
the
area-CodeGen-coreclr
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsCodeGen pull requests (PRs) automatically or manually trigger various AzDO pipelines, such as superpmi-diffs, superpmi-replay, Antigen, Fuzzlyn. These pipelines in particular produce results in Markdown format that are exposed in the AzDO UI in an "Extensions" page. This work item is to enable a mechanism where these pipelines can post back to the triggering GitHub issue the contents of the Extensions page, or some other bespoke GitHub results summary. This would make the results easier to find (it would not be necessary to search for the results in the AzDO UI), and the results would be retained longer (as the AzDO results have a very short retention lifetime). Related: #81838 category:eng-sys
|
|
There’s an AzDO task for creating GitHub issue comments: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/github-comment-v0?view=azure-pipelines |
CodeGen pull requests (PRs) automatically or manually trigger various AzDO pipelines, such as superpmi-diffs, superpmi-replay, Antigen, Fuzzlyn. These pipelines in particular produce results in Markdown format that are exposed in the AzDO UI in an "Extensions" page.
This work item is to enable a mechanism where these pipelines can post back to the triggering GitHub issue the contents of the Extensions page, or some other bespoke GitHub results summary. This would make the results easier to find (it would not be necessary to search for the results in the AzDO UI), and the results would be retained longer (as the AzDO results have a very short retention lifetime).
Related: #81838
category:eng-sys
theme:super-pmi
skill-level:intermediate
cost:medium
impact:medium
The text was updated successfully, but these errors were encountered: