Introduction
This is a series of articles related to Source Control or Version Control issues, from stand-alone apps, such as MS SourceSafe, to Server apps, such as MS TFS (Team Foundation Server), to web services, such as GitHub, AWS, and MS Azure DevOps. We tried categorizing this article series as Source Control or Version Control. Still, this site does not have these categories, so we make the articles in Category 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 complements 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 AzureDevOps
- Boards
- Repos
- Pipelines
- Test Plans
- Artifacts
- GitHub
- AWS GitHub Enterprise
- MS AzureDevOps
- Distributed App
- Git
Because these are huge topics, I will not go step by step. Instead, I write any section when I feel ready for it, but each section will be relatively independent to become a reading unit.
- Source Control (1), MS Source Safe ---Stand Alone App
- Source Control (2), MSTFS --- Centralized Server App
- Source Control (3), MSAzure DevOps (GitHub, Jira)--- Centralized Service
- Source Control (3-1), DevOps and Different Products---This article
- Source Control (4), Git --- Distributed App
- Source Control (4-1), Git --- Configuration
- Source Control (4-2), Git --- Configured to Connect to DevOps and GitHub
- Source Control (4-3), Git --- Cherry Pick in Visual Studio
- Source Control (4-4), Git ---Recover Git Tree: Reflog/Reset
- Source Control (4-5), Git ---Recover Deleted Branch
- Source Control (4-6), Git ---Revert
- Source Control (4.7), Git --- Get Specific Version or Commit
- Source Control (4.8), Git --- Get Specific Version or Commitin practice
- Source Control (4-9), Git ---Merge: Fetch, Pull, Push and Sync
- Source Control (5), GitHub access (setup connection)
- Source Control (6), DevOps access (setup connection)
- Source Control (7), GitLab access (setup connection and Clone to Local)
- Source Control (8), Git, Azure Repos, and Visual Studio (Interaction)
- Source Control (9), Push into Git Hub and DevOps
- Source Control (10), Git Hub, DevOps Publish
Introduction
This series of articles originally and mainly discusses source control issues, whatever tool we use, such as SourceSafe, TFS, DevOps, and Git. However, we put these series under the DevOps category. However, we expand the discussion into the DevOps field through deep discussion. At this point, we should have an overall understanding of DevOps, especially when we use different DevOps tools; we should know what DevOps is. I made this article to discuss this issue. We are starting with the concept of DevOps and ending with the different tools used by DevOps.
The content of this article will be
- A: Introduction
- B: DevOps
- B - 1: What DevOps is
- B - 2: History
- B - 3: Demo of DevOps Tools
- C- Tools(Products)
- C - 1: MS DevOps
- C - 2: GitHub
- C - 3: GitLab
- C - 4: Jira
B - DevOps
DevOps is quite a confusing concept. It is not a method, not a tool, not a ... any unique staff; it is a combination of several something, a collection of something; it is also a dynamic process including some actions in it. Let us start now.
B-1.What is DevOps?
Before we discuss DevOps, we should know, What DevOps is.
This series of articles the first one was published on September 27, 2021, in Source Control (8), Git, Azure Repos, and Visual Studio. At that time, we got the DevOps definition from Wiki like this.
"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 complements Agile software development; several DevOps aspects came from the Agile methodology."
It is said: "DevOps is a set of practices that ..."
Now, if we click the same link, we get something different:
"DevOps is a methodology in the software development and IT industry. Used as a set of practices and tools, DevOps integrates and automates the work of Software development(Dev) and IT operations (Ops) to improve and shorten the systems development life cycle. DevOps is complementary to agile software development; several DevOps aspects came from the agile way of working."
It is said, "DevOps is a methodology that..."
The exact definition is still under discussion and development.
Other than it being a cross-functional combination of the terms and concepts of "development" and "operations", academics and practitioners have not developed a universal definition for the term "DevOps". Most often, DevOps is characterized by key principles.
- shared ownership,
- workflow automation, and
- rapid feedback
My Understanding
Defining DevOps as a methodology is easy, but it does not cover what DevOps is. Maybe defining it as a set of Practices is better; however, it is a bit hard to understand.
Let us consider Tesla workshop,

This is a Tesla auto pipeline.

The second view of the Tesla Pipeline.

Compared with Azure pipelines.

The tasks of Azure pipelines.

We may conclude, what DevOps is.
DevOps is an A pipeline and the related, including
- Operations
- Auto development
- Auto Deployment
- Tasks
- Boarding
- Code repository
- pipeline
- Testing
- deployment
- Tools
- Azure Azure DevOps, since02/01/2010
- GitLab, since04/07/2005
- GitHub, since04/07/2005
- Jira
- Git, since04/07/2005
We may shorten it as DevOps is a software automation process.
B-2.History
Around 2007 and 2008, concerns were raised by those within the software development and IT communities that the separation between the two industries, where one wrote and created software entirely separate from those that deployed and supported the software, was creating a fatal level of dysfunction within the industry.
In 2009, the first conference, named DevOps Days, was held in Ghent, Belgium.
In 2012, a report called "State of DevOps" was first published by Alanna Brown at Puppet Labs.









Join the conversation! Your thoughts help the community grow.