-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Publish dotnet/runtime using standard Arcade Publish tooling #111934
Publish dotnet/runtime using standard Arcade Publish tooling #111934
Conversation
…n. Don't copy workloads packages as they're already in the right format now.
…ic jobs publish specific packages
…specific packages
…es. Use that when possible for unique names and produce our own names when necessary.
…o the Artifacts items in Signing.props
…lob paths to make that work
…e signed coming out of runtime and otherwise we'd miss signing them
…g/internal/_git/dotnet-runtime into standard-arcade-publish-with-join
I've updated this PR to provide a mechanism for us to merge it today and get rid of the long-running patch. Here's my basic approach:
I have a passing official build from this PR here: https://dev.azure.com/dnceng/internal/_build/results?buildId=2657037&view=results |
New official build for a314fc3 at https://dev.azure.com/dnceng/internal/_build/results?buildId=2657219&view=results |
<PropertyGroup Condition="'$(EnableDefaultRidSpecificArtifacts)' == ''"> | ||
<!-- Source-build always needs all artifacts to be published. --> | ||
<EnableDefaultRidSpecificArtifacts Condition="'$(DotNetBuildSourceOnly)' != ''">false</EnableDefaultRidSpecificArtifacts> | ||
<!-- Short-stack builds should always only publish RID-specific artifacts. --> | ||
<EnableDefaultRidSpecificArtifacts Condition="'$(ShortStack)' == 'true'">true</EnableDefaultRidSpecificArtifacts> | ||
<!-- If no override is specified, don't use RID-specific publishing. Instead, publish everything. --> | ||
<EnableDefaultRidSpecificArtifacts Condition="'$(EnableDefaultRidSpecificArtifacts)' == ''">false</EnableDefaultRidSpecificArtifacts> | ||
</PropertyGroup> |
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.
These settings make sense to me but wouldn't they better fit into the VMR orchestrator as they aren't specific to runtime?
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.
Yes, they do fit better in the VMR. However, we need to put them here first so they don't break the VMR until I change the VMR to pass these options down (also in PR)
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.
Once the VMR controls are in, I'll come back and remove these.
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.
Consider filing a tracking issue and linking to it. Also, so that others can follow along and understand the potential for improvement in these code paths.
Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.com>
/ba-g timeouts unrelated |
Publish the assets from dotnet/runtime using the standard Arcade publish tooling. This tooling doesn't allow any duplicate packages, so change our publishing logic to the following:
Publishing.props
).Blocked on MicroBuild fixes for Linux and Mac: dotnet/source-build#4793As per #111934 (comment), we are no longer blocked on this.Verified in https://dev.azure.com/dnceng/internal/_build/results?buildId=2629649&view=results that all of the same assets that we expect to produce in a runtime official build are produced on this branch.
Fixes #102672
Fixes #1719