CircleCI: Use explicit Gradle options to prevent out of memory errors #9075
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
1 task
loremattei
approved these changes
Jan 23, 2019
Contributor
loremattei
left a comment
loremattei
left a comment
There was a problem hiding this comment.
CircleCI is green :-)
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.
Although CircleCI is pretty stable, there have been occasional failures (e.g. here and here) caused by out of memory errors.
This adds some explicit options to keep Gradle under control when running on CircleCI. It includes a workaround for a Kotlin compiler crash (https://youtrack.jetbrains.com/issue/KT-15562).
Its possible the memory config is a bit conservative (only 1.5GB) but I would rather have it stable and increase from there to get better performance.
To test:
Update release notes:
RELEASE-NOTES.txt.