Conversation
Speculative change to resolve gradle/gradle#3318
bsideup
approved these changes
Dec 3, 2018
Member
bsideup
left a comment
bsideup
left a comment
There was a problem hiding this comment.
You could also set a global env var with Gradle property
Member
Author
|
Cheers @bsideup, I think I'll keep as is for now, as it's fairly explicit. |
Member
|
It's probably better to do it in env var later, since we might forget to disable it when adding new jobs (it's a tiny thing of course). So like |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
All branches on Travis CI have been failing in the Docker-in-Docker part of the build, with error logs similar to those shown in gradle/gradle#3318. It's hard to tell what's happening, but I'd like to try disabling the Gradle daemon: I suspect that the problem is due to the Gradle caches being accessed concurrently by the daemon from the install phase and the docker-in-docker phase.
As it's hard to really tell exactly what's going on, I'd like to try merging this and see if it stabilises things - I think it's pretty harmless and so far seems to work better.