Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

NOTE: This plugin was previously called: EASE Plugin (ease-plugin).


Plugin Information

View Arxan MAM Publisher on the plugin site for more information.

Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

This plugin adds the ability to publish updates of mobile apps to Apperian App Management as part of the Jenkins build process.

Usage

When you install this plugin, you will have the ability to add the "Arxan MAM Publisher" as a post-build action on a project's Configure page.

After adding the action to your project, configure it to specify the values that Jenkins will use to publish the app to Apperian during the build process. For more information, see Jenkins Integration.

Version History

Version 2.2 (2019-03-6)

  • Correctly check user permission when choosing API Token

Version 2.1 (2019-02-14)

  • Fixed a bug where publishing would fail if the job is running on a slave node.

Version 2.0 (2018-11-13)

  • Plugin renamed from EASE Plugin to Arxan MAM Publisher.
  • Build Step renamed from 'Apperian Plugin' to 'Arxan MAM Publisher'.
  • Removed PHP API URL for 'Custom URLs' environment.
  • Changed from using Username/Password to using API Token for Authentication. For more information, see Manage API Tokens.
  • Added Application Name, Short Description, and Long Description as editable fields.
  • Binary Metadata is now updated after uploading a new app version.
  • Added the ability to reapply policies when updating an app.
  • Added Pipeline support.

Version 1.2.6 (2015-05-17)

  • Added possibility to update metadata and extract it from Android, iOS, Blackberry and other file types.

Version 1.2.3 (2014-04-21)

  • Initial release.

2 Comments

  1. Unknown User (blackhornet)

    Actually if the upload is skipped due to missing arguments, the build is still successful.

    Is there a way to mark a build as failed if the upload was skipped?

    1. Unknown User (mlandry)

      Hi Unknown User (blackhornet)! This issue is now fixed with the 2.0 update.