All about Pipeline

 What is Pipeline: A pipeline is an automated process to quickly move applications from development through testing to deployment. The continuous integration and continuous delivery (CI/CD) phases are at the beginning of the pipelines.

Release Pipeline: A release pipeline specifies the end-to-end release process for an application to be deployed across a range of environments. Deployments to each environment are fully automated by using jobs and tasks. Ideally, you do not want new updates to the applications to be exposed to all the users at the same time. It is a best practice to expose updates in a phased manner i.e. expose to a subset of users, monitor their usage and expose to other users based on the experience the initial set of users had.

Various stages of Release pipeline:

Stages are the major divisions in your release pipeline: "run functional tests", "deploy to pre-production", and "deploy to production" are good examples of release stages. A stage in a release pipeline consists of jobs and tasks.

The Continuous Integration portion of the pipeline is dominated by the development group. The Continuous Delivery portion of the pipeline is dominated by the quality assurance group.

Build Pipeline: A Build Pipeline is used to generate Artifacts out of Source Code. A Release Pipeline consumes the Artifacts and conducts follow-up actions within a multi-staging system. It is best practice to establish a link between a Build Pipeline and the corresponding Release Pipeline.


Source : https://academy.pega.com/ & https://learn.microsoft.com/
Picture source : https://academy.pega.com/