0

We are currently using gradle-release-plugin.

Our release builds are twice as long due to unit and integration tests being run on both "SNAPSHOT" version and after the branch is "tagged".

here is the command line we execute in our release trigger:

./gradlew --info clean build release -Prelease.useAutomaticVersion=true

I read the plugin code and the doc and found "buildTasks" configuration but didn't find documentation or examples on them.

I'm sure we do something wrong but can't figure out what.

Thanks in advance

Pascal Gehl
  • 1
  • don't do a build in your cmd line. Instead use `./gradlew --info clean release -Prelease.useAutomaticVersion=true` . The reason is that the release task does a build during the release process. What actually happens is that you clean and then build your project but the release plugin as the third task then changes your version and triggers a build which is run because the project version did change. Both build task runs are doing a run of tests. – Hillkorn Sep 30 '22 at 19:10

0 Answers0