Flow the DotNetBuildOrchestrator property to the DependencyPackageProject inner build #1067
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
…jects inner build
mthalman
reviewed
Oct 29, 2024
mthalman
approved these changes
Oct 29, 2024
NikolaMilosavljevic
approved these changes
Oct 29, 2024
ViktorHofer
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Related to dotnet/source-build#4701
The underlying issue is that the
DotNetBuildOrchestratorproperty is not being passed to the inner build of theDependencyPackageProject. This in turn causes arcade to restore the intermediate packages which don't exist in the n-1 artifacts.Test build (Microsoft internal link) that shows the change unblocks the SBRP build in an offline leg.