Switch to assetless build for official builds #64515
Merged
+2
−32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
area-infrastructure
wtgodbe
changed the title
Copilot finished reviewing on behalf of
wtgodbe
November 24, 2025 18:01
Contributor
There was a problem hiding this comment.
Pull request overview
This PR transitions the ASP.NET Core repository to an assetless build configuration to accelerate commit flow to the Virtual Monolithic Repository (VMR). Since ASP.NET Core no longer ships via the official build, this change eliminates unnecessary asset publishing operations and removes build dependencies that previously blocked the publish-build-assets job from executing.
Key Changes
- Simplified publish-build-assets job by removing all
dependsOnconditions, allowing it to run immediately - Added
isAssetlessBuild: trueparameter to indicate no shipping assets are produced - Removed dependencies on Windows, macOS, Linux builds, code signing, tests, and source indexing jobs
Comments suppressed due to low confidence (1)
.azure/pipelines/ci.yml:731
- The post-build template is missing the
isAssetlessBuild: trueparameter. For consistency with the assetless build approach, this parameter should be added to the post-build template parameters to ensure it also skips asset publishing operations (via the-SkipAssetsPublishingflag). AddisAssetlessBuild: trueafter line 731.
- template: /eng/common/templates-official/post-build/post-build.yml@self
parameters:
publishingInfraVersion: 3
enableSymbolValidation: false
enableSigningValidation: false
enableNugetValidation: false
publishInstallersAndChecksums: true
publishAssetsImmediately: true
ViktorHofer
approved these changes
Nov 24, 2025
Member
ViktorHofer
left a comment
ViktorHofer
left a comment
There was a problem hiding this comment.
Not sure this works. Double check post-merge.
Member
Author
Will do - I just copied what SDK did: https://github.com/dotnet/sdk/pull/49113/files |
Member
Author
|
/backport to release/10.0 |
Contributor
|
Started backporting to |
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of dotnet/dotnet#711, fixes #64510. We don't ship via the official build anymore. Making our build assetless allows aspnetcore commits to flow to the VMR much quicker after merging.