[release/9.0-staging] Run outerloop pipeline only for release branches, not staging/preview #115011
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
I noticed we were sending 30k workitems each day to various Helix queues, this is due to the outerloop pipeline having a schedule triggere which matches old preview branches or the staging branches. This fixes that and also sets it so that the trigger only applies if there are actual source changes.
ghost
added
the
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
|
CI trigger only change, tell mode, adding servicing-approved |
|
/ba-g fast merge since this isn't tested in PRs. |
akoeplinger
approved these changes
Apr 24, 2025
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.
Backport of #114971 to release/9.0-staging
/cc @akoeplinger
Customer Impact
I noticed we were sending 30k workitems each day to various Helix queues at the same time, causing a heavy load on the system. This is due to the outerloop pipeline having a schedule trigger which matches old preview branches or the staging branches.
This fixes that and also sets it so that the trigger only applies if there are actual source changes.
Regression
Testing
CI testing
Risk
None, this is just a CI schedule change.