Reducing the prConcurrentLimit to 2
#2201
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
As runners are scarce in the `cloudfoundry` org, we want to limit the number of concurrent PRs. Every renovate PR gets rebased after every commit to main for [good reasons](https://docs.renovatebot.com/configuration-options/#rebasewhen). This means if there are the default `10` PRs open concurrently, merging one PR currently triggers at least 9 * 31 = 279 workflows. I chose the value of `2` so that if one PR fails to validate consistently there's a second slot for other PRs. If two PRs fail to validate consistently, probably a deeper look is necessary anyways.
|
Kudos, SonarCloud Quality Gate passed!
|
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.
As runners are scarce in the
cloudfoundryorg,we want to limit the number of concurrent PRs.
Every renovate PR gets rebased after every commit to main for
good reasons.
This means if there are the default
10PRs open concurrently,merging one PR currently triggers at least 9 * 31 = 279 workflows.
I chose the value of
2so that if one PR fails to validateconsistently there's a second slot for other PRs. If two PRs
fail to validate consistently, probably a deeper look is necessary
anyways.