Add a no-delay provisioner strategy to bring nodes online immediately#122
Open
nhunsperger wants to merge 2 commits intojenkinsci:masterfrom
Open
Add a no-delay provisioner strategy to bring nodes online immediately#122nhunsperger wants to merge 2 commits intojenkinsci:masterfrom
nhunsperger wants to merge 2 commits intojenkinsci:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The default node provisioner strategy in Jenkins is conservative and only provisions new nodes under sustained
demand. The implicit assumption is that busy executors will become free. This does not happen when using
the run-once retention strategy or when limiting job runs to 1. As a result, the default strategy unnecessarily
causes delays starting new jobs.