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.

Sign up for GitHub

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

Jump to bottom

Support incremental builds #3666

Open
MichaelSimons opened this issue Oct 19, 2023 · 1 comment
Open

Support incremental builds #3666

MichaelSimons opened this issue Oct 19, 2023 · 1 comment
Labels
area-product-experience Improvements in the end-user's product experience Epic Groups multiple user stories. Can be grouped under a theme.

Comments

@MichaelSimons
Copy link
Member

MichaelSimons commented Oct 19, 2023 •
edited by mmitche
Loading

With the introduction of the VMR, incremental build support is required to provide a productive development environment where developers want to work. Developers should be able to make repo source changes and rebuild quickly.

Today if you build the VMR, make a source change, and then rebuild, the changes code will not get detected and rebuilt. This is because of the current semaphore implementation. It requires intimate knowledge of the semaphore files and manual deletion in order to get completed build stages to rerun.

The ideal solution is a developer can build the vmr, make a src change anywere, rebuild and only the affected src is rebuilt along with all downstream dependencies.

T-Shirt Size: Medium/Large
@dotnet-issue-labeler dotnet-issue-labeler bot added area-build Improvements in source-build's own build process untriaged labels Oct 19, 2023
@MichaelSimons MichaelSimons added area-product-experience Improvements in the end-user's product experience and removed area-build Improvements in source-build's own build process untriaged labels Oct 19, 2023
@MichaelSimons MichaelSimons moved this from Backlog to Post 8.0 / Pre 9.0 in .NET Source Build Oct 19, 2023
@MichaelSimons
Copy link
Member Author

This has some overlap with #928 but I think the VMR changes the UX requirements a bit in addition to the source-build state being quite different. #928 is in a way focused on a particular solution versus a desired UX.

@MichaelSimons MichaelSimons moved this from Post 8.0 / Pre 9.0 to 9.0 in .NET Source Build Nov 14, 2023
@tkapin tkapin mentioned this issue Jan 11, 2024
Open
@mmitche mmitche added Epic Groups multiple user stories. Can be grouped under a theme. and removed Epic Groups multiple user stories. Can be grouped under a theme. labels Jan 11, 2024
@tkapin tkapin added the Epic Groups multiple user stories. Can be grouped under a theme. label Jan 15, 2024
@MichaelSimons MichaelSimons moved this from 9.0 to In Progress in .NET Source Build Feb 6, 2024
@MichaelSimons MichaelSimons moved this from In Progress to 9.0 in .NET Source Build Feb 7, 2024
@mthalman mthalman mentioned this issue May 21, 2024
Merged
@MichaelSimons MichaelSimons moved this from 9.0 to 10.0 in .NET Source Build Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-product-experience Improvements in the end-user's product experience Epic Groups multiple user stories. Can be grouped under a theme.
Projects
.NET Source Build
Status: 10.0
.NET Unified Build
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@MichaelSimons @mmitche @NikolaMilosavljevic @tkapin