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

Deduplicate assets produced on multiple build legs in the VMR to only be produced on the 'primary' build leg #60792

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jkoritzinsky
Copy link
Member

Deduplidate assets produced on multiple build legs in the VMR

As part of moving way from a "primary" vertical concept in the VMR, we need to deduplicate the Java and NPM assets that aspnetcore produces in the VMR builds. This PR provides that infrastructure.

Description

Changes the version files, Java artifacts, and NPM artifacts to all be published in the VMR only when we're publishing all artifacts, not only RID-specific ones.

Contributes to dotnet/source-build#4905

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Mar 7, 2025
Copy link
Contributor

Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at.

@jkoritzinsky jkoritzinsky marked this pull request as ready for review March 7, 2025 01:01
@Copilot Copilot bot review requested due to automatic review settings March 7, 2025 01:01
@jkoritzinsky jkoritzinsky requested review from wtgodbe and a team as code owners March 7, 2025 01:01

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

- If we're building outside of the VMR, publish these assets from the Windows job.
- If we're building inside the VMR, publish these assets from whichever job is producing non-RID-specific artifacts.
-->
<PublishAllBuildsAssetsInThisJob Condition="('$(OS)' == 'Windows_NT' and '$(DotNetBuildOrchestrator)' != 'true')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have we considered that some npm packages using gyp stuff (native libs) are platform specific? In a long dependency chain, chances of such an npm cannot be ignored.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I know, ASP.NET Core has been shipping the npms from their Windows build for years now and there hasn't been an issue. If one arises, then we can address this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants