Mobile Apps CICD Script




The tool provides an example of how the application deployment APIs of Workspace ONE UEM can be used for iOS and Android apps. This script can be used to automate application delivery to your end-user devices in the following cases:

  1. Add new apps with appropriate assignments
  2. Add new versions with appropriate assignments for existing apps
  3. Add new assignment groups to existing apps (Note: This can be done only for apps that were added by executing this script)


To execute the script, dependencies have to be installed. This tool uses Python's PIP installation system. Dependencies can be installed by executing the following command: pip install -r requirements.txt

How to execute the script file has to be updated with appropriate values before executing the script. This file has settings like the environment URL, WS1 tenant, smart group, etc.

Command to execute the script

1. Adding a new application

python <options> <File Path> <Application Name> <Build Information> <Deployment Types> <Push Mode> <Retire Previous Version> <Supported Models> <Device Type>

Application Deployment workflow needs the following required parameters:

  1. File Path - Absolute file path of the application.
  2. Application Name - Name of the application.
  3. Build Information - Comma separated Build Project Name and Build Number. (Ex: "My App Build Project,1")
  4. Deployment Types - Supported values are Alpha, Beta, and Prod. These are the assignment groups. Multiple values can be given as a comma-separated value. (Ex: "Alpha,Beta")

Build Information is used to track which Apps and builds are being uploaded and promoted.

Optional parameters: options - Three options are available.

  1. -h/ -- Help: Gives the details on how to use the script.

  2. -v {Value}/ --Version {Value} : Use this option to provide a custom numeric version(Up to 3 digits), if the actual file version is a alpha numeric version or it is a 4 or more digits version (Ex: python -v "1.0.0" "app.apk" "Android App"" "App Build Project,1" "Alpha,Beta")

  3. Retire Previous Version - This is a flag that can hold True/False. This is set to False by default. If this set to True, previous version of the app that is going to be deployed will be retired.

  4. Supported Models - This is a list of device models that the app supports. (This is a required parameter in case of Windows Universal App - appx). Supported values are Android, iPhone, iPod Touch, iPad, Windows Phone 8, Windows Phone 10, Desktop, HoloLens

  5. Device Type - Supported Device Type(This is a required parameter in case of Windows Universal App - appx). Supported values are Android, Apple, windowsphone8, winRT

Currently, the first time when an app is published with Alpha deployment mode an appdetails.json file is created in the working directory and has the app, productid, build information, version and deployment type details. This is being used in the script to decide what state the app deployment is for a particular build.

Example: {"45": {"app_id": 483, "product_id": 0, "app_version": "5.73.0", "current_deployment": "Prod"}}

2. Adding new assignments for an existing app

python -a(or -AppID) <App ID> <Build info> <Deployment Types> <Push Mode>

Example: python -a "1234" "App Build Project,2" "Alpha,Beta,Prod" "Auto"

Here, "1234" is the App ID and "Alpha,Beta,Prod" are the new deployment types(assignment groups) to which this app will be assigned.

Integrating with Jenkins is a python script that has been written to fetch jenkins build information.

This script can be integrated with jenkins as follows:

  1. Download and install jenkinsapi library by executing the command pip install jenkinsapi
  2. Fill in the Build server details in
  3. Configure the post build action in the build pipeline
  4. Provide the absolute path of for Build Information argument.

Integrating the Script with a Build Server

The script can be integrated with any build server as follows:

  1. To integrate the script, fill in the Build server details in
  2. Write a Python script to call an appropriate Build Server API to get the build information.
  3. Add a post build action in the build pipeline
  4. Provide the absolute file path of the Build Server API client written in place of argument.


End to End test cases have been added under the folder 'testing'. Please refer ReadMe file under testing folder for more details on how to run the test cases.

EndPoints Used

  1. CHUNK_UPLOAD_URL = '/api/mam/apps/internal/uploadchunk'
  2. APP_UPLOAD_URL = '/api/mam/apps/internal/begininstall'
  3. APPLICATION_SEARCH_URL = '/API/v1//mam/apps/search'
  4. APPLICATION_ADD_ASSIGNMENT_URL = '/api/mam/apps/internal/{application_id}/assignments'
  5. APPLICATION_EDIT_ASSIGNMENT_URL = '/api/mam/apps/internal/{application_id}/assignments'
  6. RETIRE_APPLICATION_URL = '/api/mam/apps/internal/{application_id}/retire'
  7. APPLICATION_DETAILS_URL = '/api/mam/apps/internal/{application_id}

Sign in to be able to add comments.

Comments 0