Establish runtime-diagnostics pipeline #113169
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The idea behind this pipeline is to pull in dotnet/diagnostics in order to supply live runtimes to diagnostics test runs. Although it will run on a schedule, the primary reason to have this is for PR validation when making changes we know could impact the diagnostics repo. Note that this change is bare bones in order to establish the pipeline in AzDo.
There was a problem hiding this comment.
PR Overview
This PR establishes a new runtime diagnostics pipeline to run live diagnostics tests using the dotnet/diagnostics repository for PR validation and scheduled diagnostic runs.
- Introduces a new YAML pipeline configuration under eng/pipelines/runtime-diagnostics.yml
- Configures scheduled runs at two different times
- Adds an external resource reference to the dotnet/diagnostics GitHub repository
Reviewed Changes
| File | Description |
|---|---|
| eng/pipelines/runtime-diagnostics.yml | New pipeline YAML file with schedule and resource configuration |
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
eng/pipelines/runtime-diagnostics.yml:21
- There are multiple 'schedules' keys defined in the YAML file. This might lead to one of the schedule configurations being ignored; consider merging them under a single schedules key to ensure all schedules are applied as intended.
schedules:
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
jkoritzinsky
approved these changes
Mar 5, 2025
This was referenced Mar 5, 2025
|
/ba-g Unable to extract a specific error message from unrelated failure. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea behind this pipeline is to pull in dotnet/diagnostics in order to supply live runtimes to diagnostics test runs. Although it will run on a schedule, the primary reason to have this is for PR validation when making changes we know could impact the diagnostics repo.
Note that this change is bare bones in order to establish the pipeline in AzDo.