Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
There was a problem hiding this comment.
🟢 Approval recommended
The change is a minimal, low-risk update to the branch include list and matches the existing trigger pattern used for other release branches.
Pull request overview
Updates the Azure Pipelines performance workflow trigger configuration so perf runs can be started automatically from the release/11.0 branch, aligning it with existing release branch triggers.
Changes:
- Added
release/11.0to thetrigger.branches.includelist ineng/pipelines/performance/perf.yml.
File summaries
| File | Description |
|---|---|
| eng/pipelines/performance/perf.yml | Adds release/11.0 to branch triggers so the perf pipeline runs on that release branch. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
|
@jkotas seems like this branch is protected, could we get this looked at and merged? |
|
Infra-only change |
|
@LoopedBard3 just curious, why don't you set I also noticed that |
Use release/*.0 for perf.yml per #133428 (comment), and limit perf-build.yml and perf-slow.yml CI triggers to main. This should make it so we don't need to make release branch specific changes going forward. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Description
Enables release/11.0 branch automatic runs in the .NET Perf Lab.
Testing
This matches previous updates of a similar goal: #117994
Risk
If this is incorrect, we will get more errors in our automatic runs and may need to remove this update.