[PERF] Update main performance pipeline triggers - #133634
Merged
akoeplinger merged 1 commit intoSep 11, 2026
Merged
Conversation
Use release/*.0 for perf.yml and limit perf-build.yml and perf-slow.yml CI triggers to main. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
|
Azure Pipelines: Successfully started running 6 pipeline(s). 10 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The trigger changes are small, consistent with existing pipeline patterns (e.g., other pipelines already use release/*.0), and introduce no apparent correctness or maintainability issues.
Pull request overview
Updates performance pipeline CI triggers to reduce maintenance and align branch matching with the established release/*.0 convention used elsewhere in eng/pipelines.
Changes:
- Replace explicit
release/X.0trigger entries inperf.ymlwith a singlerelease/*.0wildcard. - Restrict
perf-build.ymlandperf-slow.ymlCI triggers tomainonly by removing release branch includes.
File summaries
| File | Description |
|---|---|
| eng/pipelines/performance/perf.yml | Switches trigger branch list from enumerated releases to release/*.0. |
| eng/pipelines/performance/perf-slow.yml | Removes release branch triggers so CI runs only on main. |
| eng/pipelines/performance/perf-build.yml | Removes release branch triggers so CI runs only on main. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Lite
This was referenced Sep 11, 2026
Open
akoeplinger
approved these changes
Sep 11, 2026
LoopedBard3
added a commit
that referenced
this pull request
Sep 17, 2026
## Summary Add `release/*.0` to the CI branch filter in `eng/pipelines/performance/perf-slow.yml` so current and future mainline release branches trigger slow performance runs alongside `main`. Scheduled runs remain main-only. Path filters, batching, job configuration, `perf.yml`, and `perf-build.yml` are unchanged. Follow-up to #133634 and relates to #133726 (comment). ## Validation - Parsed the updated YAML and checked 12 branch-matching cases locally. - Confirmed the upstream PR diff contains only the one-line CI branch filter addition. - `git diff --check` passed. - No runtime build or tests were run for this pipeline-only change. The Azure pipeline has not been executed for this change. > [!NOTE] > This change and PR description were generated with GitHub Copilot. --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
jtschuster
pushed a commit
to jtschuster/runtime
that referenced
this pull request
Sep 18, 2026
## Summary Add `release/*.0` to the CI branch filter in `eng/pipelines/performance/perf-slow.yml` so current and future mainline release branches trigger slow performance runs alongside `main`. Scheduled runs remain main-only. Path filters, batching, job configuration, `perf.yml`, and `perf-build.yml` are unchanged. Follow-up to dotnet#133634 and relates to dotnet#133726 (comment). ## Validation - Parsed the updated YAML and checked 12 branch-matching cases locally. - Confirmed the upstream PR diff contains only the one-line CI branch filter addition. - `git diff --check` passed. - No runtime build or tests were run for this pipeline-only change. The Azure pipeline has not been executed for this change. > [!NOTE] > This change and PR description were generated with GitHub Copilot. --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.