Optionally use max parallelism value from the client settings API #5132
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tarunramsinghani
approved these changes
Mar 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: Currently the default parallelism is set to 192, which is very high for busy machines. This causes timeouts and out of memory errors. There is an existing per-pipeline variable that can override this, but we cannot override the default globally without changing the agent.
Bug 2247830: DownloadPipelineArtifact throws OOMException
Description: This uses our existing client settings API to set the default if it is not overridden on a pipeline level. if the client setting is not available, it remains at the 192 default.
Risk Assesment(Low): We already use client settings for multiple other variables and it is only used if it is set and available and the value is not already overridden.
Added unit tests: (N)
Additional Tests Performed: Manually tested all permutations of pipeline variable override set/not set and client setting set/not set.