Increase the heap of the Gradle runner #41083
Closed
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
The Gradle Daemon actually running the build does so with a 2GB heap. This PT changes the heap configuration of the gradle process that talks with the daemon to trigger the builds and relies the messages. Relates to elastic#41061
alpar-t
added
>non-issue
:Delivery/Build
|
Pinging @elastic/es-core-infra |
|
Aren't these files generated when we update the gradle version we use? How do we ensure the changes are propagated then? |
|
@rjernst that's right we would have to come up with something to make sure this is not lost. That's why I'm not marking the issue closed yet, but would like to get some certainty that this is indeed the heap that runs out and the new values work better. |
|
I'm fairly sure that OOM is coming from the grade cli not the daemon, unfortunately there's no way to keep this customization in the wrapper script to see if it helps, so I will move to configure this in CI instead |
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.
The Gradle Daemon actually running the build does so with a 2GB heap.
This PT changes the heap configuration of the gradle process that talks
with the daemon to trigger the builds and relies the messages.
Relates to #41061