Skip to content

Remove msbuild parallelism after Helix Job Monitor enablement #131614

Description

@jkoritzinsky

Today, we override the max MSBuild parallelism for the runtime tests' send-to-helix project because we have many stress pipelines that submit many jobs to Helix from one AzDO job. As the AzDO machines only have 2 CPUs, we need to override the max parallelism to ensure that we launch all jobs in parallel (and don't wait for some jobs to finish before submitting more).

The penalty for only submitting 2 jobs at a time is a lot less that the penalty for only running 2 jobs at a time, so the infra simplification should be worth a very minor slowdown (on the scale of seconds/minutes instead of hours) for infra simplification.

Originally posted by @jkoritzinsky in #129690 (comment)

Metadata

Metadata

Labels

Type

No type

Projects

Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions