-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Build the PGO build legs through the global build job template #92296
Conversation
…instrument flag instead of setting the property manually.
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsContributes to moving our official builds to using single jobs per runtime + configuration + platform combo. Also, remove the support for PGO instrumentation in the individual build jobs as we're only going to use it through the global build job in this change. Official build at: https://dev.azure.com/dnceng/internal/_build/results?buildId=2271314&view=results
|
…xproj for internal optimization pipelines (we don't use it).
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.
Only question - does it preserve teh package names correctly?
Yep! The resulting package names are identical to the prior implementation. |
Looks like these were missed in dotnet#92296
Looks like these were missed in #92296. This fixes superpmi-collect.
Contributes to moving our official builds to using single jobs per runtime + configuration + platform combo.
Also, remove the support for PGO instrumentation in the individual build jobs as we're only going to use it through the global build job in this change.
Official build at: https://dev.azure.com/dnceng/internal/_build/results?buildId=2271602&view=results