[ci] remove maxParallel limits on Azure DevOps #3725
Merged
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
StrikerRUS
approved these changes
Jan 4, 2021
|
This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Trying to take the non-controversial changes off of #3672 to make that PR smaller, and to get some changes onto
masterwithout needing to wait on that PR.This PR is based on #3672 (comment)
Per https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema%2Cparameter-schema#job,
maxParallelin an Azure DevOps pipeline config controls the maximum number of jobs to try to run simultaneously. This limit might be useful if you have some autoscaling set up or if you had some reason to want to slow down, but for our purposes it would be better to just let the default limits work and try to max out the utilization of the Microsoft-hosted runners.This change shouldn't change anything about our current CI, since we already set
maxParallelexactly equal to the number of matrix jobs. But it means that in the future when we add / remove Azure jobs, this will be one less thing that has to be changed.