Some CI environments that support builds for a wide variety of projects maintain multiple java installations (usually for different jdk versions). In such environments, using the JAVA_HOME environment variable to locate the proper keytool executable won't work. This provides an optional alternative way to specify the the java home through a project extension, i.e.
Some CI environments that support builds for a wide variety of projects maintain multiple java installations (usually for different jdk versions). In such environments, using the JAVA_HOME environment variable to locate the proper keytool executable won't work. This provides an optional alternative way to specify the the java home through a project extension, i.e.
keytool { javaHome = '/my/java/home' }