Releases: gradle/gradle-enterprise-build-validation-scripts
Releases · gradle/gradle-enterprise-build-validation-scripts
Development release
Important
The distributions of the Develocity Build Validation Scripts prefixed with gradle-enterprise
are deprecated and will be removed in a future release. Migrate to the distributions prefixed with develocity
instead.
- [NEW] TBD
2.7.1
Important
The distributions of the Develocity Build Validation Scripts prefixed with gradle-enterprise
are deprecated and will be removed in a future release. Migrate to the distributions prefixed with develocity
instead.
- [FIX] Scripts fail for Gradle 7.0.2 and older under certain conditions
2.7
Important
The distributions of the Develocity Build Validation Scripts prefixed with gradle-enterprise
are deprecated and will be removed in a future release. Migrate to the distributions prefixed with develocity
instead.
- [NEW] All user-facing text is updated to use Develocity naming
- [NEW] Add distributions prefixed with
develocity
and deprecate those prefixed withgradle-enterprise
- [NEW] Add command line argument
--develocity-server
and deprecate--gradle-enterprise-server
- [NEW] Add command line argument
--enable-develocity
and deprecate--enable-gradle-enterprise
- [FIX] Gradle builds are configured using the legacy Gradle Enterprise API resulting in deprecation warnings
- [FIX] Enabling Develocity fails for builds that already apply the Develocity plugin
2.6
- [NEW] Predictive Test Selection is disabled when running builds
- [NEW] Full support for both Gradle Enterprise and Develocity branded plugins and extensions
2.5.1
- [FIX] Error when fetching build scans for experiment summary using Develocity 2023.3.2
2.5
- [NEW] Use
CLIENT_JAVA_HOME
environment variable to control the JVM used to analyze the Build Scan data - [NEW] Drop support for Gradle Enterprise versions older than 2023.2 when using
-e
command line option - [FIX] Informs the Gradle Enterprise Gradle plugin it is being applied externally when using
-e
command line option - [FIX] API requests do not allow time for build scans to become available
- [FIX] Build caching configuration is not applied to child builds
2.4
- [NEW] Explanations of the performance characteristics are available and linked from the experiment summary
- [NEW] Infrastructure to run local experiments without publishing build scans is put in place
2.3.5
- [FIX] Scripts inject Gradle Enterprise Maven extension 1.17 which requires just released GE 2023.1
2.3.4
- [FIX] Logging level when fetching Build Scan data from Gradle Enterprise is incorrect
- [FIX] Experiments accepting Build Scan URLs incorrectly parse Build Scan ID when path contains extra parts
- [FIX] Summary shows project name as unknown when access to Gradle Enterprise API is not configured
2.3.3
- [NEW] Performance characteristics includes the serialization factors of both builds
- [FIX] Negative values for build time savings render incorrectly