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

Investigate parallelizing x64/x86 build job #17599

Open
wtgodbe opened this issue Dec 5, 2019 · 3 comments
Open

Investigate parallelizing x64/x86 build job #17599

wtgodbe opened this issue Dec 5, 2019 · 3 comments
Assignees
Labels
affected-few This issue impacts only small number of customers area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework severity-minor This label is used by an internal tool task
Milestone

Comments

@wtgodbe
Copy link
Member

wtgodbe commented Dec 5, 2019

The x64/x86 leg of our CI builds is currently the long pole. It builds x64, then x86, then some components that require both. We should investigate if it's possible to have x64 and x86 run concurrently in separate legs, then have a 3rd leg which restores the artifacts of both, and proceeds with the build of the installers & whatnot.

CC @aspnet/build @rynowak

@wtgodbe wtgodbe self-assigned this Dec 5, 2019
@wtgodbe wtgodbe modified the milestones: 5.0.0, 5.0.0-preview1 Dec 5, 2019
@rynowak
Copy link
Member

rynowak commented Dec 5, 2019

Do we really need to go that far? I suppose I was wondering if there's redundant work between the x64 and x86 steps, ie: building all of the managed code twice. I think it would be helpful to get a picture of what the current stuff does.

@javiercn javiercn added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Dec 5, 2019
@wtgodbe wtgodbe modified the milestones: 5.0.0-preview8, Backlog Aug 4, 2020
@ghost
Copy link

ghost commented Aug 4, 2020

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@wtgodbe wtgodbe added affected-few This issue impacts only small number of customers severity-minor This label is used by an internal tool task labels Dec 7, 2020 — with ASP.NET Core Issue Ranking
@wtgodbe
Copy link
Member Author

wtgodbe commented Dec 21, 2021

@dougbu assigning this to you as it's similar to what you're doing w/ removing redundant build jobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected-few This issue impacts only small number of customers area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework severity-minor This label is used by an internal tool task
Projects
None yet
Development

No branches or pull requests

7 participants
@pranavkm @rynowak @dougbu @javiercn @wtgodbe @mkArtakMSFT and others