JIRA: https://jira.spring.io/browse/INT-4019 * Add `org.gradle.daemon=true` to `gradle.properties` * Add `--no-daemon` to CI plans, such as `master` and `nightly` * Adjust `.travis.yml` to disable `gradlew assamble` task and allow artifacts caching Add `script` to `.travis.yml` config Since we have sometimes the problem with cached dependencies and the Travis report doesn't reflect the reality properly, add `--refresh-dependencies` to avoid such a caching bottleneck Also add `--parallel` for experiment to see if a new Gradle and Travis can overcome that now No `--parallel` Doesn't work forTravis. It indicates the maximum load for CPU as a critical error and interrupts the spawned Gradle Threads Add `--no-daemon` This option does not make sense for Travis. It starts a new environment for each build. Meanwhile looks like `caching` and `--refresh-dependencies` do their premise
7 lines
231 B
Properties
7 lines
231 B
Properties
#Fri Apr 29 11:02:42 EDT 2016
|
|
distributionBase=GRADLE_USER_HOME
|
|
distributionPath=wrapper/dists
|
|
zipStoreBase=GRADLE_USER_HOME
|
|
zipStorePath=wrapper/dists
|
|
distributionUrl=https\://services.gradle.org/distributions/gradle-2.13-bin.zip
|