Gotchas

Challenge 2: Setting up Development Workflow

Branching Policies

• You cannot do branching policies on private GitHub Repos
• Problem Setting up a review team did not auto assign reviewers. (in CODEOWNERS file)

Answer

• Need to ensure that the team has access to the REPO

Challenge 3: Implement Continuous Testing

Problem when running a pipeline from ADO you get an error about parallel jobs

Answer

• Accept the default billing for the organization. (org owner)
• Add at least 1, in our case 5 concurrent public agents.

Problem when auto creating bugs in the ADO boards

Answer

• We didnt set the AreaPath and Iteration correctly. You can use a keyword '@CurrentIteration' to use the current iteration.
• Note. Defects were unparented

Challenge 4: Implement Continuous Deployment

Stumbling Block

Ensured that for this effort we used the Azure Container Registry rather than the Github packages that we had found and started to use.

• Setting up the Identity for GitHub to use when interacting with Azure. We set up service principal / app registration. Made the service principal a contributor to the resource group.

• We had to change the deployment center configuration so that it would use the resource's managed identity to perform the pull.

• (We setup one of the resources managed identities to have access to pull images from the registry. We did not have to do it for the other 3)

• When specifying the branch within the yml file we were using $default-branch which never worked for us. We hardcoded to main

• We had to modify the health check code to not loop infinitely and exit with 1 (to break the deployment and stop) exit with 0 on 200's to successfully stop

When we were checking the APIs health check we assumed that the root GET would return something. It did not.

• We used the wrong urls for health checks.

• Green Blue Deployments

• We didn't add the resource group name on the swap command.

• We did not add the staging slot name to all of the swap commands.