We decided to preinstall JDK 17 on the build stacks (both Linux and macOS), so you don’t have to install it manually and lose time waiting for the process. There are a few requirements to keep in mind though: JDK17 on Bitrise VMs
An app built with Gradle running on JDK17 can still run on Android devices with earlier runtimes (because 'minSdkVersion' and 'compileSdkVersion' controls the app’s behavior) RequirementsĬhanging the JDK version and the garbage collector are relatively quick tasks to improve build speeds compared to huge refactors or other long initiatives.
The Java runtime on an Android device is independent of the runtime used to build the app on a developer machine. The JDK version used for running Gradle does not affect the final application in any way. We benchmarked the performance of JDK11 and JDK17 on Android builds with the default settings, then with an alternative garbage collector enabled.īased on the results we decided to preinstall JDK 17 on the build stacks (both Linux and macOS), so you can benefit from the improvements (JDK 11 remains the default though). The inspiration for this experiment was an article about the performance improvement of recent JDK versions. JDK11 is 3 years old though, and the current LTS (Long Term Support) release is JDK17. Gradle and the Android tooling run on Java, and the minimum required JDK (Java Development Kit) version to run these tools is 11 at the moment, and this is the default on Bitrise stacks as well. After benchmarking build times for 3 projects with different JDK versions, JDK 17 is now also preinstalled on all build stacks to help you get the 9-20% speed improvements we did. Speed up Android build times with simple tweaks to the Java Development Kit and Gradle.
0 kommentar(er)
