-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[release/8.0-staging] Fix publishing PGO assets #102527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/8.0-staging] Fix publishing PGO assets #102527
Conversation
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
|
It was decided not to merge this at the moment to avoid resetting the runtime build. |
117896c to
987ce19
Compare
|
Retargeted to staging so as to not require resetting the build (as it will only get into the next servicing build). |
|
I see it's just a yaml change. Do we still need this to go through Tactics? Does this modify the shipped bits? |
|
This does not modify shipping bits. It only modifies non-shipping PGO bits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can treat is as tell-mode now that it is targeting staging. Feel free to merge if the CI looks good.
Backport of #92958 to release/8.0
/cc @jkoritzinsky
Infrastructure fix for publishing PGO assets. When backporting other work for the 1ES Pipelines move, this follow-up PR was missed, which broke publishing assets from the PGO legs.
Customer Impact
[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Regressed with #102097
Testing
[How was the fix verified? How was the issue missed previously? What tests were added?]
We have high confidence in this fix as the same PR provided a fix for the corresponding change in main.
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]
Low risk