WALA/travis/script-gradle

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

case "$TRAVIS_OS_NAME" in
  (linux) headless=xvfb-run ;;
  (osx) headless='' ;;
esac

$headless ./gradlew --continue --no-build-cache --stacktrace \
	  "$submodule"build \
	  "$submodule"javadoc \
	  lintGradle
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 --`

macOS doesn't seem to have "xvfb-run", and may not need it anyway 2018-02-09 02:55:28 +00:00			`case "$TRAVIS_OS_NAME" in`
			`(linux) headless=xvfb-run ;;`
Fix a shellcheck warning when setting a variable to the empty string 2018-03-05 17:56:32 +00:00			`(osx) headless='' ;;`
macOS doesn't seem to have "xvfb-run", and may not need it anyway 2018-02-09 02:55:28 +00:00			`esac`

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			`$headless ./gradlew --continue --no-build-cache --stacktrace \`
			`"$submodule"build \`
			`"$submodule"javadoc \`
			`lintGradle`