Source Control (3), MS Azure DevOps

This is a series of articles related to Source Control or Version Control issues, from the stand-alone apps, such as MS SourceSafe, to Server app, such as MS TFS (Team Foundation Server), to web services such as GitHub, AWS, and MS Azure DevOps. We tried to category this series of articles as Source Control or Version Control, but this site does not have these categories, so we make the articles in Category as DevOps, as explained in the wiki.

DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary with Agile software development; several DevOps aspects came from the Agile methodology.

The structure of this article series will cover,

  • Stand Alone App:
    • MS Source Safe
  • Server App
    • MS TFS (Team Foundation Server)
  • Online (Cloud) Centralized Service:
    • MS Azure: DevOps
      • Boards
      • Repos
      • Pipelines
      • Test Plans
      • Artifacts
    • GitHub
    • AWS GitHub Enterprise
  • Distributed App:
    • Git

Because these are huge topics, I will not go step by step, instead, I will write any section when I feel I am ready for it, but each section will be relatively independent.

Introduction

This article was written on 9/21/2021, I mainly recorded some of my previous experiences. Recently, I viewed one brief introduction for DevOps, I've add that info into this article.

The structure of discussion will be

  • Introduction
  • A: Introduction to DevOps
    • A-1: What DevOps is
      • GitHub
      • Jira
    • A-2: Why DevOps, Service vs. Server
    • A-3: Diff between DevOps (online Service) and TFS (promise Server)
  • B: Components for DevOps
    • B-0: Overview
    • B-1: Boards
    • B-2: Repos
    • B-3: Pipelines
    • B-4: Test Plan
    • b-5: Artifact
  • Summary

A: Introduction to DevOps

We will discuss what DevOps is, Why DevOps, and the diff between DevOps and TFS Server.

A-1: What DevOps is

We have given the DevOps definition at the beginning of this article, we will repeat it below, and also give the definitions for several other similar products, such as GitHub, Jira Software, basically, they are similar, and can be described in one sentence as:

A Software development Management software (or service, or platform).

DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary with Agile software development; several DevOps aspects came from the Agile methodology.

GitHub, offers the distributed version control and source code management (SCM) functionality of Git, plus its own features. It provides access control and several collaboration features such as bug trackingfeature requests, task managementcontinuous integration and wikis for every project.

Jira Software is built for every member of your software team to plan, track, and release great software.

Note
The histories of above and related,

  • MS DevOps: 02/01/2010
  • Jira: 2002
  • Git: 04/07/2005

A-2: Why DevOps --- compared to TFS

Note
The main timeline for MS Visual SourceSafe (1995), TFS (2005), VSTS (2014), DevOps (2018)

A-3: Diff between DevOps and TFS server

B: Components for DevOps

 

from Microsoft,

B-0: Overview

B-1: Azure Boards

B-2: Azure Repos

B-3: Azure Pipeline

Pipelines

B-4: Azure Test Plans

B-5: Azure Artifacts

Summary

DevOps usually are used by entire development teams, including development and QA, and the business people, In detail,

  • Boards: Dev team, QA team, + business people
  • Repos: Dev + QA
  • Pipeline: Dev
  • Test Plan: QA
  • Artifact: open to external people to share.

Reference