This repository is maintained by the Gradle Enterprise Solutions team, as one of several publicly available repositories:
- Gradle Enterprise Build Configuration Samples
- Gradle Enterprise Build Optimization Experiments
- Gradle Enterprise Build Validation Scripts (this repository)
- Gradle Enterprise Open Source Projects
- Common Custom User Data Maven Extension
- Common Custom User Data Gradle Plugin
- Android Cache Fix Gradle Plugin
The purpose of the build validation scripts is to assist you in validating that your Gradle and Maven builds are in an optimal state in terms of maximizing work avoidance. The build validation scripts do not actually modify your build, but they surface what can be improved in your build to avoid unnecessary work in several scenarios.
Each script represents a so-called experiment. Each experiment has a very specific focus of what it validates in your build. The experiments are organized in a logical sequence that should be followed diligently to achieve incremental build improvements in an efficient manner. The experiments can be run on a fully unoptimized build, and they can also be run on a build that had already been optimized in the past in order to surface potential regressions.
There are currently five experiments for Gradle and four experiments for Maven. You could also perform these experiments fully manually, but relying on the automation provided by the build validation scripts will be faster, less error-prone, and more reproducible.
The build validation scripts are available as pre-built, executable Bash scripts. The build validation scripts are bundled and documented separately for Gradle and Maven. There are specific instructions on
- how to use the build validation scripts for Gradle
- how to use the build validation scripts for Maven
You can also assemble the build validation scripts from source by running ./gradlew build from the root folder of this repository.
Once the build has finished successfully, you can find two .zip files in the build/distributions folder: one .zip file containing the build validation scripts for Gradle and one .zip file containing the build validation scripts for Maven.
If the build fails with You need the 'autom4te' utility, then you will need to install 'autoconf' before you can run the build successfully. For example, on macOS with Homebrew, you can install autoconf with brew install autoconf.
If the build fails with Error while executing shellcheck: docker: Cannot connect to the Docker daemon, then you will need to install and launch Docker before you can run the build successfully.
Visit our website to learn more about Gradle Enterprise.
The Gradle Enterprise build validation scripts are open-source software released under the Apache 2.0 License.