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

Determine how to build aspnetcore's hosting bundle #52884

Open
Tracked by #3739
mmitche opened this issue Dec 18, 2023 · 2 comments
Open
Tracked by #3739

Determine how to build aspnetcore's hosting bundle #52884

mmitche opened this issue Dec 18, 2023 · 2 comments
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework area-unified-build

Comments

@mmitche
Copy link
Member

mmitche commented Dec 18, 2023

ASPNetCore's hosting bundle requires some x86 and x64 artifacts to build. If we went with a relatively strict set of verticals, we would not build the x86 and x64 bits on the same machine. That means the hosting bundle will need to be built in the join. Questions that need answering:

  • How is it built at the VMR join?
  • How is it still built at repo level for validation purposes? How do we sink the join lower in the stack for repo-level validation?

T-Shirt size: Medium This is part of the other join point item.

@mmitche mmitche converted this from a draft issue Dec 18, 2023
@gfoidl gfoidl added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Dec 20, 2023
@wtgodbe
Copy link
Member

wtgodbe commented Jan 9, 2024

2 or 3 years ago, I investigated doing parallel x64/x86 builds w/ a join job at the end: #17599. It turned out to actually be slower, because the time we saved by parallelizing was lost thru artifact upload/downloads, and machine provisioning. It did work, though, so if this is just about fitting VMR build requirements & we don't mind losing a few minutes of build time, this is definitely doable.

@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@wtgodbe wtgodbe removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@wtgodbe wtgodbe removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 13, 2024
@dotnet dotnet deleted a comment from dotnet-policy-service bot Feb 13, 2024
@dotnet dotnet deleted a comment from dotnet-policy-service bot Feb 13, 2024
@wtgodbe wtgodbe added this to the .NET 9 Planning milestone Feb 13, 2024
@mmitche
Copy link
Member Author

mmitche commented Sep 25, 2024

@directhex This is an option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework area-unified-build
Projects
Status: No status
Development

No branches or pull requests

4 participants