Azure Devops

This topic explains in detail the Integration between Appdome and Azure DevOps Pipeline.

To successfully secure your applications with Appdome from Azure DevOps platform, you can either use "Appdome build-2secure" extension, or use Appdome DEV-API.

build-2secure action - Recommended

With this action, you can easily secure and customize your mobile apps on Azure DevOps, including signing your app with your own enterprise certificate for added flexibility and control. No coding or technical expertise is required.

For detailed information about integrating "Appdome build-2secure" action into your Azure DevOps workflow, please follow: Appdome build-2secure KB


To successfully use Appdome DEV-API in GitHub environment, please follow the below steps:


An Appdome account
Appdome’s token
Fusion-Set ID
An Azure DevOps account
An active repository

azure-pipelines.yml file located on Azure DevOps Pipline.

If Pipeline does not exist:

  1. On your Azure DevOps project, click on "Pipelines" tab.
  2. Then click on "New pipeline" button.
  3. Next, click on, "Github YAML" and select a repository.
  4. Select Starter pipeline, it will open the azure-pipelines.yml file.
  5. Copy this snipped code to your new workflow file

API implementation


# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:

- main

  vmImage: ubuntu-latest


- script: |
    publicLink=$(curl -s --request GET --url "" --header "Authorization: <API-Token>");

    curl -s -X PUT "$(echo "$publicLink" | jq -r .url)" --header 'Content-Type: application/x-compressed-tar' -T <app-file-name>;

    app=$(curl -s --request POST --url "" \
    --header "Authorization: <API-Token>" --header 'content-type: multipart/form-data' \
    --form file_name=<app-file-name> --form file_app_id="$(echo "$publicLink" | jq -r .file_id)");

    task_id=$(curl -s --request POST --url "" \
    --header "Authorization: <API-Token>" --header 'accept: application/json' --header 'content-type: multipart/form-data' \
    --form action=fuse --form fusion_set_id=<fusion_set_id> --form app_id="$(echo "$app" | jq -r .id)");

    task_id="$(echo "$task_id" | jq -r .task_id)";
    echo "task-id: $task_id";

  displayName: 'Upload and Build none protected application'

Continue with implementing each part of the build process as documented in the How to section.