In the given article we will learn via demonstration how to use Azure DevOps, its concept, primary technologies and step-by-step process with proper examples including diagrams and screenshots for better understanding. Followed by some FAQ’s with solutions.

In simple words, The concept of Azure DevOps is based on Software as a service (SaaS) which aims to reduce human efforts by automating the development and testing of an application.

DevOps is not just a role, job title, methodology, or piece of software. DevOps is a field that takes skills from Development and Operations to create and run applications more effectively.

Azure DevOps is a comprehensive platform that encompasses various primary technologies and services to support the software development lifecycle. These technologies include:

• Azure Boards: Azure Boards is a work-tracking system that helps teams plan, track, and discuss work across the entire development process. It offers features like backlogs, sprint planning, and work item tracking.
• Azure Repos: Azure Repos provides version control services for managing the source code. It supports Git repositories, enabling distributed version control and collaboration among development teams.
• Azure Pipelines: Azure Pipelines is a powerful CI/CD (Continuous Integration/Continuous Delivery) service that automates the build, test, and deployment of the applications.
• Azure Test Plans: Azure Test Plans is a testing framework that allows you to plan, track, and manage your testing efforts. It includes test case management, manual testing, exploratory testing, and more.
• Azure Artifacts: Azure Artifacts is a package management service that allows you to store, publish, and share packages (e.g., NuGet, npm) and container images with the team and the broader organization.
• Azure Security Center: Azure Security Center helps you protect your applications and data by providing advanced threat protection across all Azure services. It offers security recommendations and threat detection capabilities.

How to Use Azure DevOps

Now we’ll see via demonstration, how we actually use Azure DevOps step-by-step process from scratch by considering a simple html code. Assuming we have successfully created a free Azure DevOps account.

Step 1: After creating a free Azure DevOps account for free, create a project to get started.

Step 2: After creating project we can see the primary technologies on the left bar as we have discussed. We go the repos to add the code/application to the Azure DevOps via multiple options such as shown below.

For the demonstration we are considering a single page HTML as an application to proceed and get more insights about the DevOps rather than focusing on the application.

Step 3: After importing the code, it will reflect into the repos section as follows:

Step 4: Now we head onto the boards section, Here we can add a new task in New work item section. For example we want to add contact us page, so we add it as a task with suitable description and save it.

Now under the boards, we get 3 columns, where we can maintain our issue and slide it to “doing” & “done” section as per progress.

Step 5: In the repos file, we can have a track over the branches to the master with the implemented changes that were given as task which can be reviewed and merge to the master , and in the commit section we can see the timestamped changes.

Step 6: Once we have integrated everything and done with the coding part then we can create a pipeline which will push this piece of code which will actually reach out to the user.

First we connect our final code,

Afterwards we select then configure the code and then we review before final save & run. This is how we create a pipeline and the job is queued now.To release the pipeline, we go to the releases under pipelines section, click on new pipeline then add an Artifacts and select the project as follows:

After that we options to add stage where we can use multiple features like Azure App Service deployment and many other as follows:

Step 7: Test Plans- It is not included with the free account, with the use of it we can do the actual browser testing which is available by the Microsoft Azure.

Step 8: Artifacts- Suppose we have our own piece of code which we want to integrate, we go to “connect to feed” from there we add our piece of code to the azure project we are dealing with. As follows:

That was all for the work flow done in step by step in Microsoft Azure DevOps handling both development and operational parts.

Frequently Asked Questions (FAQs)

1. How does Azure Pipelines support CI/CD?

Ans: Azure Pipelines is a CI/CD system that automates the building, testing, and deployment of applications. It integrates with various source code repositories and can be used to create and manage pipelines for building, testing, and releasing software automatically.

2. What is the difference between Azure DevOps Services and Azure DevOps Server?

Ans: Azure DevOps Services is a cloud-based, fully managed service, while Azure DevOps Server (formerly known as Team Foundation Server or TFS) is an on-premises solution. The core functionalities are similar, but Azure DevOps Services offers additional features and automatic updates.

3. How can I integrate third-party tools with Azure DevOps?

Azure DevOps offers a wide range of integrations and extensions through the Azure DevOps Marketplace. You can find integrations for various third-party tools, such as issue tracking systems, build systems, and monitoring solutions.

4. What is the pricing model for Azure DevOps?

Azure DevOps offers a range of pricing options, including a free tier for small teams, and paid plans that are based on the number of users and usage. You can find the most up-to-date pricing information on the Azure DevOps website.

5. What is Azure Repos, and how does it handle version control?

Azure Repos is a version control system that provides Git and Team Foundation Version Control (TFVC) repositories. It allows teams to collaborate on code, track changes, and manage source code using Git or TFVC, providing branching, merging, and code review capabilities.