Bump to a medium+ resource class for CI builds #3455
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
Our builds are running at max CPU and RAM for most of the CI build. We could probably get some improvement from more resources.
|
Resource usage looks much better with this bump up to the next step. I'm hoping this can avoid some of the failures we have been seeing lately of builds suddenly dying without a clear cause. |
shakuzen
changed the title
|
|
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.
Our builds are running at max CPU and RAM for most of the CI build on the default
mediumresource class for docker executors. We could probably get some improvement from more resources. This bumps up one level tomedium+and makes the resource class choice explicit in the build, instead of the implicit default.