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

Force building of Mono manifest packages when building via source-build #81790

Merged
merged 4 commits into from
Feb 9, 2023

Conversation

directhex
Copy link
Contributor

No description provided.

@ghost
Copy link

ghost commented Feb 7, 2023

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

null

Author: directhex
Assignees: directhex
Labels:

area-Infrastructure-libraries

Milestone: -

@ViktorHofer
Copy link
Member

cc @tmds as that's the opposite of what you are doing in #81480. Should we also inline this property into the repo's config?

@tmds
Copy link
Member

tmds commented Feb 8, 2023

cc @tmds as that's the opposite of what you are doing in #81480. Should we also inline this property into the repo's config?

Yes, that makes it easier to reproduce the source-build configuration from ./build.sh without going through arcade, see #81480 (comment).

@ViktorHofer
Copy link
Member

@directhex please move that property out of SourceBuild.props and into another location, i.e. Directory.Build.props before Subsets.props are imported.

@directhex
Copy link
Contributor Author

@ViktorHofer so conditionally set the ForceBuildMobileManifests property, based on DotNetBuildFromSource, in Directory.Build.Props?

@ViktorHofer
Copy link
Member

Yes, exactly. But before the Subsets.props import as that file reads the property.

@directhex
Copy link
Contributor Author

E2E tested locally w/ VMR

@directhex directhex changed the title We can't pass source-build properties externally, they need to come via SourceBuild.props Force building of Mono manifest packages when building via source-build Feb 9, 2023
@directhex directhex merged commit 917f407 into dotnet:main Feb 9, 2023
@steveisok
Copy link
Member

/backport to release/8.0-preview1

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2023

Started backporting to release/8.0-preview1: https://github.com/dotnet/runtime/actions/runs/4135266103

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2023

@steveisok backporting to release/8.0-preview1 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: We can't pass source-build properties externally, they need to come via SourceBuild.props
Applying: Indicate that we can consume emsdk manifest via source-build
Using index info to reconstruct a base tree...
M	eng/Version.Details.xml
Falling back to patching base and 3-way merge...
Auto-merging eng/Version.Details.xml
CONFLICT (content): Merge conflict in eng/Version.Details.xml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 Indicate that we can consume emsdk manifest via source-build
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2023

@steveisok an error occurred while backporting to release/8.0-preview1, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

steveisok pushed a commit to steveisok/runtime that referenced this pull request Feb 9, 2023
dotnet-bot pushed a commit to dotnet/dotnet that referenced this pull request Feb 12, 2023
… building via source-build

Backport of dotnet/runtime#81790

Original commit: dotnet/runtime@7deac7d

[[ commit created by automation ]]
@ghost ghost locked as resolved and limited conversation to collaborators Mar 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants