jobs: We have two jobs called Debug and Release.

Later we will add another stage called Deploy Stages: This is where we define our stages. variables: We have defined two global variables which can be reused in our stages.trigger: We trigger our pipeline whenever a change happens to the main branch.Here’s a rough explanation of the structure of the above file. Steps : - template : ionic -android -release -build.yml # Release build - job : Build_Ionic_Android_Release Steps : - template : ionic -android -debug -build.yml Jobs : # Debug build - job : Build_Ionic_Android_Debug Variables : vmImageName : 'windows-latest' projectName : 'SampleApp' stages : - stage : BuildĭisplayName : Build Ionic - Android projects Your file structure should look like this.įor our initial step, we will create the barebones structure of our azure-pipelines.yml file I will explain why we do this in a second. We will then add two additional YAML files called ionic-android-debug-build.yml and ionic-android-release-build.yml. We will use this folder to keep all our Azure Pipeline line YAML files. Let’s first create a folder called infrastructure at the root of our solution structure. Creating the initial structure of the azure-pipelines.yml If you make any changes to your Ionic project, you can use the ionic cap copy command to copy any changed web assets or ionic cap sync if you are using/updated any native dependencies.Īfter these steps, your project structure should look like the following.įor this tutorial, I will create a single azure-pipelines.yml file and build-publish two Android apps, one of Debug configuration and another for Release.ġ. 💡 It’s now recommended to keep your native projects in source control. With the initial ionic cap add android command it will copy the required web assets into the native project. We first need to issue the ionic build command before adding the Android project for the first time.

Ionic app builder