Skip to content

Stop utilizing inner clone functionality with the Unified Build plan #3072

@MichaelSimons

Description

@MichaelSimons

With Arcade powered source-build (arpow) the source code is cloned to an inner repo within the artifacts directory for the source-build repo legs. This is done to get a clean environment in order to properly detect prebuilts without disrupting the developers workspace. The inner clone never added value within the tarball but was kept in place in order to utilize a common code path between the repo legs and the tarball. This inner clone has two significant downsides.

  1. Performance - both in times of coping the source and the disk space requirements it drives.
  2. UX - when a build occurs, devs often use the paths from the errors in build logs to navigate to the offending code. If they make changes to the inner cloned code, those changes will get lost when rebuilding. The inner clone is never preserved.

The inner clone should be removed with the Unified Build plan. Perhaps it would make sense to stop the use within the VMR-lite for .NET 8.0 and within the repo build when source-build is the build in .NET 9.0.

Metadata

Metadata

Labels

EpicGroups multiple user stories. Can be grouped under a theme.area-infraSource-build infrastructure and reporting

Type

Projects

Status

Done

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions