Building Code from Multiple Repos with YAML Pipelines

You could only build code from a single repo using classic build pipelines in Azure DevOps. Now with multiple repo support added to YAML build pipelines (pipeline as code), you can decide which of the repos you want to checkout and build, in a single pipeline build sequence. Let’s see the steps in detail.

Implementing Simple and Effective Branching and Deployment Strategy with Azure DevOps

In the previous post, we have discussed, a simple and effective branching and deployment strategy as a concept. Let’s now have a look at key implementation considerations of the proposed strategy with Azure Git repos and Azure Pipelines.
Let’s have a look at pictorial representation of the proposed strategy first.

Simple and Effective Branching and Deployment Strategy

While using Git repos there many standard branching strategies teams follow. With this post let’s discuss a simple to understand and execute branching and deployment strategy, which supports most of the requirements, a software development and delivery team requires. The following implementation is considering the Azure Git Repos and Azure Pipelines in Azure DevOps. However, you might be able to implement the same with other Git repos and CI/CD tools.

Define Variables Dynamically and Use Them in Subsequent Steps in Azure DevOps Pipelines

You normally define variables in Azure DevOps pipelines in the pipeline definition or using variable groups. However, there might be situations in a given step in your pipeline you might want to set a variable with a value from external source. You do not have to define such variables in your release definition or in a variable group added to the definition. You can obtain the value from external source and dynamically define the variable, so that it can be used within the agent job. Let’s look at the steps to achieve this.

Getting Started with Secure DevOps Kit for Azure

Security is important aspect of any software development project. DevOps is essential part of software development. Improving security measures of software development, delivery and deployment is now can be enhanced with Secure DevOps kit for Azure. This security kit comes with PowerShell unitalities as well as CI CD extensions etc. for securing your software projects. Let’s explore the Secure DevOps Kit with couple of posts. In this first post let’s look at an overview as well as how to get started with Azure Subscription health scans using PowerShell utilities.

Resolving “ERROR: There was a conflict. The remote server returned an error: (403) Forbidden.” While Creating Function App in Azure in IaC

You can use Infrastructure as code (IaC) to create resources in Azure and use that in the Azure DevOps pipelines. However, if you are using IaC create an Azure function where the storage account of the function is added to Virtual Network (vnet in Azure) you may run into the issue ERROR: There was a conflict. The remote server returned an error: (403) Forbidden. To fix this issue you can set the storage account to allow any network while deploying function app and then reapply the restriction on storage access. Let’s see the cause of the error and how to resolve as the error message is really misleading.

Rollup Columns in Azure DevOps Boards

Azure Boards in Azure DevOps facilitate project planning and management with agility. The rich feature set and extensibility of Azure Boards with project level customizations as well as process template level customizations helps a lot to manage the projects effectively. The new feature rollup columns help you to visualize progress of the project work based on various criteria using the default fields as well as custom fields. Let’s have a quick look at options available with the new feature roll up columns in Azure Boards.
To add rollup columns in Azure Boards, navigate to Backlog section and select a backlog level such as User Stories backlog. Then click on Column Options.

Import BitBucket Cloud Repo to Azure Git Repo

Azure DevOps being a comprehensive Application Lifecycle Management tool provides Azure Git Repos as the distributed version control system which can be easily integrated with, Azure Boards to track requirements, and Azure Pipelines and Azure Tests, implement build and deployment automations as well as test management and test automation. If you are already a BitBucket cloud git repo user you may want to move your repos in BitBucket could to the Azure Git Repos to get the advantages it offers, with totally integrated set of Azure DevOps features. Let’s look at the steps required to import a BitBucket cloud repo with history to Azure Git Repos.