CAMMS Deployment Guide

Set Up New Environment

Part 1: Set up a pipeline

To be able to deploy the code automatically when one commit the code to the repository, we need to create a pipeline that auto deploy the code, we use a Docker image to the new environment.

In this example we create a pipeline for the Development environment. Every time a developer commit their code to the CAMMS Repo (Dev Branch) , the pipeline is triggered and pushes the code to the Development environment.

Go to https://dev.azure.com/transport-canada/Medical Certificate Processing/_build and click on create a new pipeline
Select Use the classic editor
Select the correct branch you need for the pipeline and click Continue
Under the Select a template select Empty job or Docker container
Give the pipeline a name
Under Get sources make sure to select the correct repo and branch
Under Agent job check that you have a check mark under Allow scripts to access the OAuth token
Click to add a task if you selected an empty job, if selected Docker container in step 4 you will have this task already.
Configure the first task “Build an image”. Under the Task version make sure to change it to 0.*. The Action should be Build an image. The Display name you can change to reflect building an image. Select the correct Subscription.
Select the Dockerfile by clicking on the 3 dots

Under Build Arguments add the following:

PAT=$(System.AccessToken)
FEED_URL=https://pkgs.dev.azure.com/transport-canada/_packaging/DevOps-Nuget/nuget/v3/index.json

12. Under the Image name add the environment name - pipeline name : $(Build.BuildNumber)

ncdsafsecsurcr-camms-smmac-dev:$(Build.BuildNumber)

13. Click add a new task (similar to step 8). Search for Docker container and add the task and configure the “Push an image” task. Under Task version select 0.*. Under Action select Push an image. the Display name should change to Push an image. Make sure the subscription and container are correct.

14. Repeat step 12 to configure the image name for the push an image, if not already done.

15. Save the pipeline so you won’t lose any info before continuing to the Variables.

16. Add two new pipeline variables:

BuildConfiguration              Release

BuildPlatform                   any cpu

17. Configure the Triggers: Check “Enable continuous integration”

18. Configure the options. Make sure the Build number is in the following format:

$(date:yyyyMMdd)$(rev:.r)

19. Save the pipeline and run it. At this point all should be running correctly and the code should be in the container registry under Repository.

Part 2: Set up and configure Azure AD

Setting up Azure portal involved few steps:

Activate your Developer role in order to configure Azure AD

In order to configure and view some features in Azure AD we need to activate our Developer role for the day or for few hours. To do that go to Azure Ad Privileged Identity Management