-
Notifications
You must be signed in to change notification settings - Fork 41.6k
Add Gradle Enterprise Maven Extension #22089
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Gradle Enterprise Maven Extension #22089
Conversation
|
@runningcode Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
This adds build caching and build scans. The changes required disabling scans when using the maven invoker plugin in order to not cause duplicate build scans when invoking other maven builds. There is also an empty `.mvn` folder in the spring-boot-starters project to prevent duplicate build scans as well since there is no way to pass properties to the maven-javadoc-plugin. The checkstyle plugin was causing a cache miss with the `propertyExpansion` because it contains an absolute path. The absolute path is now ignored and instead the files are added as inputs to the checkstyle plugin. This only enables the local build cache. The remote cache is not yet enabled. On my local machine: ./mvnw clean install build times go from about 30 minutes to about 10 minutes. ./mvnw clean install -Pfull build times go from about 60 minutes to about 13 minutes.
261cbb8 to
57399e6
Compare
|
@runningcode Thank you for signing the Contributor License Agreement! |
|
Thanks very much for the PR, @runningcode. This is currently blocked on spring-io/develocity-conventions#8. |
|
0.0.5 of the extension is now on Maven Central so this is no longer blocked. |
|
@wilkinsona I've updated this PR to use 0.0.5 of the Spring |
This adds build caching and build scans. The changes required disabling scans when using the maven invoker plugin in order to not cause duplicate build scans when invoking other maven builds. There is also an empty `.mvn` folder in the spring-boot-starters project to prevent duplicate build scans as well since there is no way to pass properties to the maven-javadoc-plugin. The checkstyle plugin was causing a cache miss with the `propertyExpansion` because it contains an absolute path. The absolute path is now ignored and instead the files are added as inputs to the checkstyle plugin. This only enables the local build cache. The remote cache is not yet enabled. On my local machine: ./mvnw clean install build times go from about 30 minutes to about 10 minutes. ./mvnw clean install -Pfull build times go from about 60 minutes to about 13 minutes. See gh-22089
|
Thanks very much, @runningcode. This has been merged into 2.1.x and forwards in 2.2.x. |
This adds build caching and build scans.
The changes required disabling scans when using the maven invoker plugin in order to not cause duplicate build scans when invoking other maven builds.
There is also an empty
.mvnfolder in the spring-boot-starters project to prevent duplicate build scans as well since there is no way to pass properties to the maven-javadoc-plugin.The checkstyle plugin was causing a cache miss with the
propertyExpansionbecause it contains an absolute path. The absolute path is now ignored and instead the files are added as inputs to the checkstyle plugin.This only enables the local build cache. The remote cache is not yet enabled.
On my local machine:
./mvnw clean installbuild times go from about 30 minutes to about 10 minutes../mvnw clean install -Pfullbuild times go from about 60 minutes to about 13 minutes.