Skip to content

Latest commit

 

History

History
92 lines (83 loc) · 6.26 KB

CHANGELOG.md

File metadata and controls

92 lines (83 loc) · 6.26 KB

Jenkins Android Signing Plugin

Version History

2.2.5 - 23 July 2017

  • Fix JENKINS-45714
    • Added missing concerns for finding the zipalign.exe command and Android SDK on Windows.
  • Properly override the build environment with the effective launched process environment so the plugin can find zipalign from a custom tool exported PATH element.

2.2.4 - 14 June 2017

Enhancements

  • Attempt to retrieve environment variables from a dummy process to find the zipalign utility.
    As a result, you can use the Custom Tools Plugin to install the Android SDK and export ANDROID_HOME environment variable. This is necessary because the Custom Tool plugin only adds environment variables to launched processes for a build, e.g., an Execute shell build step.
  • Search the PATH variable for the zipalign utility and potential Android SDK installations. This suggestion comes from JENKINS-41787.

2.2.3 - 30 May 2017

Minor bug fix/enhancement (JENKINS-44428)

  • Use the credentials ID in the Key Store drop-down text if the credentials description is blank.
  • Added more meaningful error log messages when things go wrong reading the key store.
  • You can now leave the Key Alias field blank/null when your key store only has one key entry.

2.2.2 - 19 May 2017

Minor bug fix (JENKINS-44299)

  • The Sign Android APKs build step form validation now catches the InterruptedException that occurs in the above issue, as well as validates all globs in a comma-separated multi-value of the APKs to Sign form field.

2.2.1 - 10 April 2016

  • Omit the -signed component of the output signed APKs for the Output to unsigned APK sibling/UnsignedApkSiblingMapping option when the unsigned APK includes the -unsigned component. This is to align with the intention of the change in the previous release to write signed APKs the same way the Android Gradle plugin does. Apologies for the excessive changes.

2.2.0 - 3 April 2016

  • Skip zipalign option - This is primarily to support signing debug APKs, for which the zipalign command fails. Choose this option in the advanced section of the config UI
  • Signed APK output option - Signed APKs are now written to the directory of the input unsigned APK by default. Change this option in the advanced section of the config UI.
    • Previously saved Sign APKs steps of Freestyle jobs will output signed APKs as before to the SignApksBuilder-out directory.
    • Pipeline scripts with signAndroidApks steps will write signed APKs in the new default manner. You can specify the old behavior like the this:
    signAndroidApks (
   // ...
   signedApkMapping: [$class: 'UnsignedApkBuilderDirMapping']
)
    • Sign APKs steps previously or newly generated from a Job DSL plugin script will write signed APKs in the new default manner. You can specify the old behavior like this:
    job('myAndroidApp.seed') {
  steps {
    signAndroidApks '**/*-unsigned.apk', {
      signedApkMapping { unsignedApkNameDir() }
    }
  }
}
  • Updated Pipeline/Workflow dependency to 2.0
  • Updated Android apksig dependency to 2.3.0 release

2.1.0 - 1 Mar 2017

This release includes some significant changes:

  • Config format change that is not backwards compatible
    • The Sign APKs build step no longer accepts multiple APK signing entries. You must instead use multiple Sign APKs build steps. However, in most cases, if you are actually signing multiple APKs, the comma-separated globs in the APKs to Sign field should cover your needs with just one build step.
    • When you install the new version of the plugin and restart Jenkins, the plugin will automatically upgrade any of your jobs that include Sign APKs build steps.
    • Be aware that you cannot downgrade the plugin after upgrading and expect your Sign APKs build step configurations to remain intact.
  • Jenkins Pipeline support - see the README
  • Job DSL support - see the README
  • As part of the the Pipeline support, the build step configuration form now offers parameters to override the ANDROID_HOME location or the Zipalign Path (ANDROID_ZIPALIGN environment variable) directly. Access these fields by clicking the Advanced button at the top of the Sign APKs form group. Zipalign Path takes precedence over ANDROID_HOME. If you don't supply either of these configuration parameters in the form, the plugin will still attempt to find them from the Jenkins system environment variables.
  • Build step form fields help on the configuration page
  • The Archive Signed APKs option now defaults to checked/true
  • Improved naming of output APKs
    • The plugin will produce signed APKs relative to the job workspace at SignApksBuilder-out/myApp-unsigned.apk/myApp-signed.apk in case you have downstream build steps that will manipulate the signed APK.
    • The plugin no longer assumes the input, unsigned APKs have a -unsigned component in the file name. If -unsigned is present, the plugin will replace it with -signed. Otherwise, the plugin will simply insert -signed before the .apk suffix.

2.0.8 - 7 Feb 2017

Minor bug fixes

  • Try using zipalign.exe if zipalign does not exist in ANDROID_HOME for Windows case
  • Expand the zipalign path with EnvVars

2.0.7 - 18 Jan 2017

This is the first release since the original plugin became unmaintained two years ago.