DevOps Pipeline (2), Import/Export And Clone

Since Microsoft introduced Azure in 2010, we have changed our computing habits a lot, basically from local or promises to cloud. This is a huge change and a huge leap. Looking back, we did have a lot of experience indirectly or directly working on or related on Azure, or associated DevOps.

In 2011, I participated in a project in Health Care field, a huge project with 10 terabytes of data in production and 5000 database transactions per second at peak time. We have 200 developers involved in this project, divided in 20 feature Agile Feature teams. We use TFS server, auto built the app when anyone checked in any changes to the server. At that time, it might not be Azure DevOps, but the operation was somewhat similar with the concept of CI (Continue Integration) and CD (Continue Deployment).
I had worked on a project, the client wanted to move all current Apps from TFS promises Server into DevOps Cloud associated with Git as source control management. We worked with MS Pipeline intensively.
Another project, with Fortify Scanning, a security scanning, we need to setup a Azure Pipeline to the automation process with Fortify as a core functionality.
Recent years, more and more companies moved or moving to Cloud, such as Azure, associated with DevOps, Pipeline.

All of them require us, even as a developer, to be familiar with Azure, and DevOps. I had article series about Source Control (Repos), this series is about Pipelines. The style of the article series is similar to the Repos series, These are not system summary, or introduction, or learning notes, these are just gathering what I have experienced and I assume I understood and shared with myself and you. The following are the topics I have now and will complete within days or weeks. Later on, I will add some more materials according to new experience or summary.

Introduction

This article topic is import/export and clone pipelines. The following is the content of this article

Introduction
Export/Import a Pipeline
- Export
- Import
- Second Sample
Clone a Pipeline
- Clone
- Second Sample

When we have an existing pipeline, and want to use it as a base or sample to build a new pipeline, if the original pipeline is in the same group, we can easily use clone to make a new one, otherwise, if not in the same group, we can use export to get a JSON file, and then import from the target group or machine.