Ben Liblit 6be7a1a8a2 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-06-26 09:19:02 -07:00
..
before-cache-gradle	"rm" on macOS apparently doesn't understand long ("--foo") flags	2018-04-18 11:29:28 -05:00
before-cache-maven	In Travis-CI, test Maven and Gradle separately and concurrently	2018-04-18 11:29:24 -05:00
before-install-gradle	In Travis-CI, test Maven and Gradle separately and concurrently	2018-04-18 11:29:24 -05:00
before-install-maven	Teach Gradle how to download "/tmp/DroidBench" when needed	2018-04-18 11:29:26 -05:00
install-gradle	Have Travis CI periodically try to build each subproject separately	2018-06-26 09:19:02 -07:00
install-maven	Use Gradle to create selected Eclipse metadata before Maven builds	2018-04-18 11:29:29 -05:00
script-gradle	Have Travis CI periodically try to build each subproject separately	2018-06-26 09:19:02 -07:00
script-maven	In Travis-CI, test Maven and Gradle separately and concurrently	2018-04-18 11:29:24 -05:00