Skip to content
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

Open
wants to merge 39 commits into
base: main
Choose a base branch
from

Conversation

jkoritzinsky
Copy link
Member

@jkoritzinsky jkoritzinsky commented Jan 28, 2025

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:

  • In a given build, publish all packages that were produced in the current build that contain that job's target RID.
  • For some target RIDs, also publish an additional subset of packages (specified in Publishing.props).
  • For some jobs (specified in runtime-official), publish all packages produced.
  • In the VMR, mark all "packages not to be published" as "Vertical" visibility so they're still available upstack.
  • Outside the VMR, skip publishing all "packages not to be published" packages.

Blocked on MicroBuild fixes for Linux and Mac: dotnet/source-build#4793

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

…n. Don't copy workloads packages as they're already in the right format now.
…es. Use that when possible for unique names and produce our own names when necessary.
@jkoritzinsky
Copy link
Member Author

I've verified that signing works for the Mac assets as expected, so we're good to go on that front (once the parallelization issues are fixed)

eng/DotNetBuild.props Outdated Show resolved Hide resolved
eng/Publishing.props Outdated Show resolved Hide resolved
eng/Publishing.props Outdated Show resolved Hide resolved
This solves problems around specifying EnableDefaultArtifacts=false in some VMR legs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure blocked Issue/PR is blocked on something - see comments
Projects
Status: No status
3 participants