Skip to content

[WIP] [NO-REVIEW] [NO-MERGE] Remove VMR inner-build concept #176

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

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

Conversation

ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Apr 10, 2025

Fixes dotnet/source-build#4249
Fixes dotnet/source-build#3789
Fixes dotnet/source-build#3807
Fixes dotnet/source-build#4184
Fixes dotnet/source-build#4444

Depends on dotnet/source-build#5006, dotnet/source-build#5034

  1. Remove the repo source-build infrastructure:
    • The outer/inner-build concept
    • The SB intermediate package creation
  2. Remove the DotNetBuildPhase property and replace its usage with the now only two inclusive properties. Update docs.
  3. Move the ArPow inner clone target into the VMR orchestrator and integrate it into the repo infra (still conditional only for SBE).
  4. Move the ArPow target that handles creating the package usage data and the package report into the VMR orchestrator
  5. Update the remaining DotNetBuild.props files with the new property, item and target names.

Extra work for which I will submit separate PRs:

  • Move the WritePrebuiltUsageData and ReportPrebuiltUsage targets that were executed only for dotnet.proj into finish-source-only.proj to better distinguish them from the newly added ArPow targets that got moved into the VMR orchestrator.
  • Place the "prebuilt-report" logs under artifacts\log\<config>\ and avoid the now unnecessary copy step in the YML.
  • Remove unnecessary SourceBuild.props / DotNetBuild.props which only contained properties that were used for repo source-build pre-built intermediate package creation.
  • Rename the remaining few SourceBuild.props to DotNetBuild.props

@ViktorHofer ViktorHofer force-pushed the RemoveInnerBuildConcept branch 9 times, most recently from 632b15f to 49725e3 Compare April 10, 2025 20:27
@ViktorHofer ViktorHofer force-pushed the RemoveInnerBuildConcept branch 3 times, most recently from 754095a to 28af55e Compare April 10, 2025 22:11
@ViktorHofer ViktorHofer force-pushed the RemoveInnerBuildConcept branch 16 times, most recently from a2c3bc4 to 609c8c6 Compare April 14, 2025 20:21
@ViktorHofer ViktorHofer force-pushed the RemoveInnerBuildConcept branch 2 times, most recently from 7cf6e3a to 84f2c79 Compare April 15, 2025 05:51
@ViktorHofer ViktorHofer force-pushed the RemoveInnerBuildConcept branch 5 times, most recently from a819eb7 to 4fe8a4d Compare April 18, 2025 17:24
1. Remove the repo source-build infrastructure:
   - The outer/inner-build concept
   - The SB intermediate package creation
2. Remove the DotNetBuildPhase property and replace its usage with
   the now only two inclusive properties. Update docs.
3. Move the ArPow inner clone target into the VMR orchestrator and
   integrate it into the repo infra (still conditional only for SBE).
4. Move the ArPow target that handles creating the
   package usage data and the package report into the VMR orchestrator
5. Update the remaining DotNetBuild.props files with the new property,
   item and target names.

Extra work:
- Move the `WritePrebuiltUsageData` and `ReportPrebuiltUsage` targets
  that were executed only for dotnet.proj into finish-source-only.proj
  to better distinguish them from the newly added ArPow targets that
  got moved into the VMR orchestrator.
- Place the "prebuilt-report" logs under "artifacts\log\<config>\"
  and avoid the now unnecessary copy step in the YML.
- Remove unnecessary SourceBuild.props / DotNetBuild.props which
  only contained properties that were used for repo source-build.
- Rename the remaining few SourceBuild.props to DotNetBuild.props
@ViktorHofer ViktorHofer force-pushed the RemoveInnerBuildConcept branch from 4fe8a4d to 8f8492c Compare April 18, 2025 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant