Skip to content

[PERF] Enable slow performance CI for mainline releases - #134104

Merged
LoopedBard3 merged 3 commits into
dotnet:mainfrom
LoopedBard3:loopedbard3-mainline-release-triggers
Sep 17, 2026
Merged

LoopedBard3 merged 3 commits into
dotnet:mainfrom
LoopedBard3:loopedbard3-mainline-release-triggers

Conversation

@LoopedBard3

@LoopedBard3 LoopedBard3 commented Sep 16, 2026

Copy link
Copy Markdown
Member

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.

LoopedBard3 and others added 3 commits September 10, 2026 13:02
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>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Include release/*.0 in perf-slow.yml CI triggers while keeping the scheduled runs main-only.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
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.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The scoped trigger update has no unresolved review issues.

Pull request overview

Enables slow performance CI for release/*.0 mainline release branches while keeping scheduled runs limited to main.

Changes:

  • Adds release/*.0 to the CI branch filter.
  • Preserves existing schedules, paths, batching, and job configuration.
File summaries
File Description
eng/pipelines/performance/perf-slow.yml Enables CI runs for mainline release branches.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

@LoopedBard3
LoopedBard3 merged commit ede9a1a into dotnet:main Sep 17, 2026
71 of 72 checks passed
@LoopedBard3
LoopedBard3 deleted the loopedbard3-mainline-release-triggers branch September 17, 2026 16:57
@dotnet-milestone-bot dotnet-milestone-bot Bot added this to the 12.0-preview1 milestone Sep 18, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants