The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page. App Management Publisher

step([$class: 'ApperianRecorder']): App Management Publisher

  • uploads
      Array / List of Nested Object
    • prodEnv : String

      Choose the production environment to which the plugin will connect. If you aren’t sure which environment to choose, contact Customer Support at

    • customApperianUrl : String
    • apiTokenId : String

      Choose an API token to use for authenticating your Apperian organization.

      To include additional tokens in this list, go to Jenkins > Credentials and add a new Global Credential. In the Kind field, choose Secret Text, set Scope to Global, and add your API token in the Secret field.

      The user associated with the API token must have valid permissions for adding apps in Apperian. For more information on user permissions, see Managing Users.

    • appId : String

      To update an existing app, choose it from this list of native apps currently stored in your Apperian organization.

    • filename : String

      Specify the filename pattern that this plugin will use to search for and upload the app file from your workspace.

      If your project builds multiple versions of the app binary (for example, signed and unsigned), use this field to explicitly specify the correct file in the workspace. For example: target/android-app-v*.apk.

    • appName : String
    • shortDescription : String
    • longDescription : String
    • author : String
    • version : String
    • versionNotes : String
    • signApp : boolean
    • credential : String

      Choose the credentials you want to use to sign the app. If no credentials are listed, or if you need to add different credentials, see Managing Signing Credentials.

      Remember, when you re-sign an iOS or Android app that was already installed on any of your users' devices, it is important that you sign it with the same signing credentials used to previously sign it.

    • enableApp : boolean
    • reapplyPolicies : boolean

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?


See existing feedback here.