Override the path of the Android SDK installation this build step should use to find the zipalign tool. You can also set the ANDROID_HOME environment variable in your Jenkins system or node configuration. E.g., /usr/local/android-sdk.

An Ant-style glob, or multiple comma-separated globs, selecting the APK files relative to the workspace. For example, myApp/build/outputs/apk/myApp-unsigned.apk or **/*-unsigned.apk or app1/**/*-unsigned.apk, app2/**/*-unsigned.apk.

Check this option to add all signed APKs this build step generates to the build's archived artifacts. If you don't want this step to archive the signed APK artifacts, downstream build steps can access signed APKs in the workspace at paths like SignApksBuilder-out/myApp-unsigned.apk/myApp-signed.apk, where myApp-unsigned.apk is a directory named for the input unsigned APK.

Check this option to add all input unsigned APKs to the build's archived artifacts. These will be the APK files selected with glob pattern(s) of the APKs to Sign setting.

The entry name of the private key/certificate chain you want to use to sign your APK(s). This entry must exist in the key store credentials the Key Store ID references. If your key store contains only one key entry, which is the most common case, you can leave this field blank.

The ID of a certificate credential. This build step expects the referenced certificate credential to be a password-protected PKCS12 file containing a key protected by the same password. See this plugin's script if you need help creating such a key store to add to Jenkins, or Google how to convert your Android release key to a PKCS12 file.

Skip the Zipalign step of signing the APK(s). This is primarily for the case of signing debug APKs, for which the zipalign command fails.

Override the full path of the Android zipalign executable this build step should use to align the target APKs. You can also set the ANDROID_ZIPALIGN environment variable in your Jenkins system or node configuration. E.g., /opt/android-tools/bin/zipalign