Skip to content

[PERF] Update mainline release pipeline triggers - #2

Closed
LoopedBard3 wants to merge 1 commit into
mainfrom
loopedbard3-mainline-release-triggers
Closed

LoopedBard3 wants to merge 1 commit into
mainfrom
loopedbard3-mainline-release-triggers

Conversation

@LoopedBard3

Copy link
Copy Markdown
Owner

Summary

  • Replace explicit release versions in eng/pipelines/performance/perf.yml with release/*.0 so current and future mainline release branches trigger automatically.
  • Restrict perf-build.yml and perf-slow.yml CI triggers to main for now by removing their existing release/8.0 and release/9.0 entries.
  • Preserve schedules, path filters, batching, and job configuration.

Follows up on dotnet#133428 (comment). This change targets dotnet/runtime:main.

Validation

Parsed all three files as YAML, checked 33 branch-filter cases, and confirmed that other pipeline settings are unchanged. git diff --check passed. Runtime builds and tests were not run because this change only updates pipeline branch filters; the pipelines have not been executed for this change.

Note

This PR description and the changes were generated with GitHub Copilot.

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>
@LoopedBard3
LoopedBard3 deleted the loopedbard3-mainline-release-triggers branch September 14, 2026 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant