fix: set a more reasonable value for bitrisescript average_task_duration #159
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
It's impossible to know the average task duration of these workers, because they entirely depend on how long the workflows take in Bitrise. It could be one minute or multiple hours. But 30 minutes seems like a reasonable middle ground. Also bump up the SLO value so we don't spin up new nodes as quickly.
bhearsum
approved these changes
Apr 16, 2024
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.
It's impossible to know the average task duration of these workers, because they entirely depend on how long the workflows take in Bitrise. It could be one minute or multiple hours. But 30 minutes seems like a reasonable middle ground.
Also bump up the SLO value so we don't spin up new nodes as quickly.
Pull Request checklist