The "One Minute DevOps" Series - Part One

Series Introduction

 
Welcome to a new series of short articles I am presenting about DevOps, specifically in the Azure DevOPs stack. The objective is that you will learn about an Azure-based DevOPs service in no more than one minute and thus, quickly get familiar with the entire stack over a short period of time. These are going short, easily digestible articles; so let's get started
 

Boards, Repos and Pipelines!

 
The One Minute DevOps - Part 1
 
The words "DevOps" is a mixture of two words 'Development' and 'Operations'. It is a mixture of methodology and process which minimizes the gap between the development and operations team to improve collaborations and productivity. It is an extremly powerful combination that helps the project team to Shorter Development Cycles, Reduced Deployment Failures, Reduced Costs, and keep development efforts transparent.

Introduction to DevOPs

On the Azure DevOps platform, a number of different components work in a tightly integrated manner to enable DevOps best practice, the first three of these are,
 

Azure DevOPs Boards 


Boards is a project planning and management tool. With Boards, Users can write Stories, Epics, Tasks, Sub-task, bugs, and carry out work progress tracking. In the screenshot below, you can see three tasks created, one for each section, “To Do”, “Doing”, and “Done”. The task can be moved from one section to another when its status changes.
 
Azure Devops Screenshot
 

Azure DevOPs Repos 


'Repos' is short for 'Repository', this is the place where you store your code. 

Azure Repos is a version control tool that helps to store and manage the source code. It supports two types of version control system, Git and Team Foundation Version Control. Repos supports a code branching strategy so that multiple users can merge the code after successful build and test cases to maintain high-quality code. The default value for version control under Repos is Git.
 
Azure repo
 

Azure DevOPs Pipelines


Azure DevOps pipeline is a combination of continuous integration(CI) and continuous delivery(CD) that can be used to automatically build, test and deploy the code from your repository to the various environments on the Azure cloud under one umbrella - think of it as the glue that ensure everything happens in a tightly controlled, and consistant manner.
 

FIND OUT MORE here.