DevOps & CI/CD are buzz words for a while now and they have really proven their value in today’s fast moving world and Agile development process. One understands the true value only when they have actually been a process of it and see for themselves the immense amount of time and headache it saves. At initially we had setup CI/CD for Android via Microsoft’s Visual Studio App Center (an upgrade of Hockey App), but last year they declared the which got us worried about the overall future of VS App Center. That was one of the reasons we wanted to switch away from it. Secondly, the free tier provided around 400 minutes of build time per month per account which would had been sufficient for other technologies, but Android takes around 15 minutes to create a single build and deploy. We all know what gradle is capable of 😉. So having multiple apps (both iOS and Android) in the same account didn’t fare well. Royale Cheese retirement of MBaas We were already using for CI/CD for other technologies and it seemed promising. It’s future plan had no issues of shutting down and it provided around 1800 minutes of free build time. We decided to give it a try and so far don’t have any complaints. We have started loving and adoring Azure DevOps and hope it stays this way. Azure DevOps Alright! Enough with the issues, let’s see how we can get the build & deployment going. In this tutorial we are going to make the newer and not .apk to upload to the Google Play Console. Android App Bundle (.aab) Prerequisites Paid , an app added to the Play Console Google developer account Azure DevOps account with an Android repository created A jks file to sign the build Continuous Integration Continuous Integration is the process of running a build & a test suite every time a change has been pushed on to the repository. Since the Android build do take a substantial amount of time and usually cloud CI/CD tools gets costly with more build time it is better to schedule a the CI pipeline once a week. I will be using a demo project named created in my devops account to create ci cd pipelines. The project has a blank activity and support Lollipop 5.0 and above. Android Open your project and navigate to section on the left panel as in the screenshot below. Pipelines Click on which will open the below page. Create Pipeline Here we are going to select which is easier than the other options. The other options will eventually lead to writing yaml files for configuring your pipelines. Use the classic editor Usually you might have dev, qa and/or uat branches to upload to the internal or beta channels on Google Play Console and you would only want to promote the app to production from your Google Play Console. So select your branch from which you want to run the build and click Continue. For me everything is on the master branch. Ideally we would be tempted to select the template and get on with our life; . Since the template doesn’t provide a way to generate an .aab file we are not going to use it. Instead select an empty job. Android Don’t Do It Android We will now have an empty to which we will be adding tasks. Agent Job 1 We are going to have to do the following tasks to create our CI pipeline: Setting up a jks file Unsigned build via gradle Generate .aab file Create an Artifact Let’s start step-by-step. Setting up a jks file If you have uploaded an apk or aab in the past to the play store you must have used a jks file to sign the build. You should the use the same jks file in this step. If you haven’t generated a file yet is a good documentation. here Get a hold of your jks file since we are going to upload it now. Click on sign besides which will open a list of tasks to add. Search for . + Agent Job 1 Download secure file Click on the button to add the task. It will give an error saying . It is asking for a secure file to be uploaded. Click on the gear/settings icon besides the field and upload your jks. We will Add Some settings need attention Secure file We will now provide a name to this file so that it can be referenced from the sign task. Click on the drop down and enter in the . This will update the to reflect the variable name. Output Variables KeyStoreFile Reference name Variables list Unsigned gradle file Click on sign besides which will open a list of tasks to add. Search for . + Agent Job 1 gradle Click on the button to add the task. We are going to turn off under section. You can keep it on as per the requirement. Secondly we are going to update the task name. Since we are going to make a release build update your task name to . If you want to build using a particular flavour you can update your task name accordingly. e.g. if you are using dev as a flavour name update your task name as . Add Publish to Azure Pipeline JUnit Test Results buildRelease buildDevRelease Generate .aab file Click on sign besides which will open a list of tasks to add. Search for . + Agent Job 1 Command line In the section clear the field and set the below text. Script jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 -keystore $(KeyStoreFile.secureFilePath) -storepass $(StorePassword) -keypass $(KeyPassword) $(system.defaultworkingdirectory)/app/build/outputs/bundle/release/*.aab $(KeyStoreAlias) There are 4 variables in the script out of which we have already set . Time to set other 3 variables , and . Navigate to the tab on the tap and add the variables and their values as shown in the screenshot below. Once you are sure that the values are correct you can click on the lock icon to secure it. Once you lock and save no one will be able to view it including you, so make sure you still have a backup of the details in case you want to use it somewhere else. KeyStoreFile.secureFilePath StorePassword KeyPassword KeyStoreAlias Variables Create an Artifact The above step creates an .aab file but still needs to be converted in to an artifact so that it is available to the CD pipeline for release. By now you are a pro at adding tasks to . Add the following two tasks to : & . To avoid confusion of which tasks to select I have added the screenshots below. Agent Job 1 Agent Job 1 Copy Files Publish build artifacts Now select the task and set in the field, .aab Contents $(build.artifactstagingdirectory) Target Folder*. Copy Files $(system.defaultworkingdirectory) Source Folder **/ in the and in the Click on and click to save our CI pipeline. Save & queue Save That is it for the . We will now head on to the to find out how to release the generated artifact to the channel on Play Console. Continuous Integration Continuous Deployment Internal Testing Continuous Deployment While Continuous Integration deals with creating a build on the machine itself, is all about how will you publish that build to the Play Store, App Store, Self-Hosted or Cloud server. In order to deploy to the Play Store you will need a Google Play Console account and an app created in Play Console with the same bundle id. Continuous Deployment Next, we will go back to our Azure DevOps project and select under the pipeline section. Releases Since there is no pre-defined template for uploading a build to the Play Store, we are going to select an empty job. We will now enter a stage name for our deployment. You can name it whatever you want. I have kept it as Play Store Deployment Let’s connect the CI artifact with our current CD pipeline. Select from the artifacts. This will open a dialog on the right to which we will select our artifact. Click the drop down for and you will see as one and only option (unless you have added more CI pipelines or altered the CI name). Add an artifiact Source (build pipeline) Android-CI Select the and click . After adding the artifact our release pipeline will look something like below. Android-CI Add Since the CI & CD pipelines are separate we should setup a way to automatically trigger the CD pipeline when the CI is successful. To achieve that select the lightning icon for the artifact we just added. This will open a dialog on the right which will have a setting to enable/disable the Continuous Deployment trigger. When the build trigger is enabled our release pipeline will automatically start when a new build is completed by our build (CI) pipeline. We are not going to enable the Pull Request trigger. So far we have setup the pipeline to start automatically when a new build is available in our build pipeline. We have also setup a Play Store Deployment stage to which we will add tasks for the actual deployment in the next section. Deployment task Select 1 job 0 task hyperlink which will switch to the Tasks tab. Select the + plus besides the to open a list of new tasks. When you search for . you will see by Microsoft. Install the item if not already installed. Once installed and when you search for Google App again you will see a few new tasks as below. Agent Job Google Play Google Play Select the task that says and click the button (Don’t select ). Some settings will need attention which we will take care of one-by-one. Google Play – Release Bundle Add Google Play – Release Adding a service connection Firstly we need to create a new service connection. Click on button besides the field. It will upon up a dialog which primarily asks for a and a . We are going to create a service account on Google Play Console to upload the build. This account will also have a private key attached to it for authentication purposes. New Service Connection Service Account E-mail Private Key To create the account visit and select under under . Google Play Console API Access Developer Account Settings Click button which will pop open a dialog as below. Create new service account Open the link in step 1 which will redirect you to a new tab of . Google Cloud Console Select on the top to start creating a new account. In the newly opened page I have entered in the service account name but it can be whatever you want. Enter the if needed. + CREATE SERVICE ACCOUNT Google Play Console service account description Click to continue. It will then ask for what permissions do you want to allocate for the user. Click the Role drop down and search for . Select the with . CREATE Owner Owner Full access to all resources Click the button and select in step 3 since we don’t want to add any users or groups who can perform actions as this service account. You will be redirected to the list of keys page. Now select the newly created account and go to the tab. Here we are going to add a new for our service connection. Continue Done Keys Private Key Select and from the drop down select . It will show a pop up of which type of key you want to create. Add Key Create new key Select the option and click button. This will ask you to download the file. Store it some place secure we are not going to use the whole file as it is, rather if you open the file it will have a key called . JSON CREATE private_key Before we use this value head back to our google play console’s page and click on button. It will refresh the list of service accounts with your service account added to the list. API Access Done For the newly created service account there will be button for that row. Click on the button which will open a page to invite the user. Don’t get confused with the term since Google has probably reused a page to display the same information for the service account. Grant access invite Click on the on the bottom right and in the pop up dialog that comes up click on . This action will redirect you to page with the service account added as a new user. Invite User Send Invite Users and Permissions We will now setup the and the in Azure DevOps. First, copy the email of the newly created service account into the in the Azure DevOps tab. Next open the private key json file and copy the value of to field. Here is what it looks like. Service Email Private key Service Account E-mail private_key Private Key Click on which will add the service connection to the field. Next enter your bundle id in the field. Finally in the you can browse to select the .aab file by clicking the 3 dots on the right. Usually the aab will at location Save Service connection Application id (com.google.MyApp) Bundle path <your CI name>/drop/app/build/outputs/bundle/release/*.aab If you haven’t run a CI pipeline yet you can set the path as $(System.DefaultWorkingDirectory)/_Android-CI/drop/app/build/outputs/bundle/release/*.aab If you are using a flavour prefix with your flavour name in the path. e.g. the path should be release $(System.DefaultWorkingDirectory)/_Android-CI/drop/app/build/outputs/bundle/devRelease/*.aab You can select which track you want to launch to from the drop down. That is all the settings you need. You can now the pipeline and run the CI pipeline to build an aab and upload it to the Play Console. Save Conclusion This seems to be a long tutorial but once you are successful in setting up the CI/CD pipelines it would be a huge time saver for your developers. Secondly, it will run on the cloud so there is no need for a physical machine. You can trigger the build from your phone by logging in to Azure DevOps. Hope you have enjoyed this article and hope it helps others in your team. To learn how to setup CI CD pipeline for iOS you can visit . this tutorial

Google

Microsoft

Target

Technical Director & Co-Founder - @Royale Cheese

2021 - HackerNoon Contributor of the Year - CICD

2022 - HackerNoon Contributor of the Year - Docker

2022 - HackerNoon Contributor of the Year - Monitoring

2022 - HackerNoon Contributor of the Year - Optimization

Explore. Learn. Connect. 

2021 - HackerNoon Contributor of the Year - AZURE

Nominated for 2022 - HackerNoon Contributor of the Year - Monitoring

Nominated for 2022 - HackerNoon Contributor of the Year - Docker

Nominated for 2022 - HackerNoon Contributor of the Year - Optimization

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

How To Set Up Azure DevOps CI/CD Pipelines for Android

How To Set Up Azure DevOps CI/CD Pipelines for Android

Too Long; Didn't Read

Companies Mentioned

Arjav Dave

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

How To Set Up Azure DevOps CI/CD Pipelines for Android

Too Long; Didn't Read

Companies Mentioned

Arjav Dave

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES