WALA/travis/install-gradle

# -*- mode: sh; sh-shell: sh -*-

# initial p2AsMaven downloads are sometimes slow
travis_wait 30 ./gradlew --dry-run

submodule=${BUILD_ONLY_SUBMODULE:+:$BUILD_ONLY_SUBMODULE:}

./gradlew --continue --no-build-cache "$submodule"assemble
In Travis-CI, test Maven and Gradle separately and concurrently This should help identify cases where the Gradle build only works if it runs before or after a Maven build. It will also help us recognize any Maven regressions accidentally introduced by our Gradle work. 2017-12-19 16:56:41 +00:00			`# -- mode: sh; sh-shell: sh --`

Tell Travis CI to be more patient during initial p2AsMaven downloads 2018-04-12 23:44:32 +00:00			`# initial p2AsMaven downloads are sometimes slow`
Tell Travis CI to be even more patient during initial p2AsMaven downloads 2018-04-13 22:19:54 +00:00			`travis_wait 30 ./gradlew --dry-run`
Tell Travis CI to be more patient during initial p2AsMaven downloads 2018-04-12 23:44:32 +00:00
Have Travis CI periodically try to build each subproject separately If Gradle dependencies are set up correctly, then it should be possible to build any subproject starting with a pristine tree. These take too long to use for every commit, pull request, etc. But running an extensive test like this periodically (e.g., weekly) seems reasonable. 2018-05-21 21:59:40 +00:00			`submodule=${BUILD_ONLY_SUBMODULE:+:$BUILD_ONLY_SUBMODULE:}`

			`./gradlew --continue --no-build-cache "$submodule"assemble`