[BEAM-4122] Tune Gradle resource usage on Jenkins #5171
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
|
This still needs evaluation, but our Jenkins environment is so flaky right now that anything will be an improvement. |
|
Run Seed Job |
|
retest this please |
|
Run Seed Job |
|
retest this please |
Our Gradle builds are frequently exhausting memory on the Jenkins lab machines. We have capped the number of workers at 2 across all jobs to limit the total memory usage per job.
|
Run Seed Job |
|
Run Java PreCommit |
|
retest this please |
10 tasks
|
I'm not able to get a good validation of this because #5180 is also working on Jenkins jobs and we're both running Seed Job. I don't know if this configuration is perfect, but it's an improvement over the current state. Can we get these merged so that they can be incorporated into #5180 as well? R: @aaltay |
aaltay
approved these changes
Apr 19, 2018
|
Run Seed Job |
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 new Gradle build seems to be exhausting memory on the Jenkins machines, causing them to lose their connection and die. This has made our tests extremely flaky.
We need to tune the Gradle build such that it does not exhaust Jenkins machine resources.
See BEAM-4122 JIRA for more details.
Follow this checklist to help us incorporate your contribution quickly and easily:
[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue.mvn clean verifyto make sure basic checks pass. A more thorough check will be performed on your pull request automatically.