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
19 lines
399 B
YAML
19 lines
399 B
YAML
language: java
|
|
jdk: oraclejdk8
|
|
sudo: false
|
|
services:
|
|
- mongodb
|
|
- rabbitmq
|
|
- redis-server
|
|
before_cache:
|
|
- rm -f $HOME/.gradle/caches/modules-2/modules-2.lock
|
|
cache:
|
|
directories:
|
|
- $HOME/.gradle/caches/
|
|
- $HOME/.gradle/wrapper/
|
|
install: true
|
|
env:
|
|
- TERM=dumb SI_FATAL_WHEN_NO_BEANFACTORY=true NO_REFERENCE_TASK=true
|
|
script:
|
|
- ./gradlew check --refresh-dependencies --no-daemon
|