![]() Picture below shows example of two TeamCity builds representing two steps in my project delivery.īuild called Acceptance tests on Staging has dependency on Deploy to Staging. When designing the Deployment Pipeline it is very important to create number of steps reflecting delivery process that have dependency on a previous Steps (checkpoints) of the process. Among many features that TeamCity have, exists the one for adding Snapshot Dependency between different builds. I’m going to take a closer look on the way TeamCity supports modelling the Deployment Pipeline. ![]() Hundson and Jenkins from the OSS community.This automation is typically handled by the Continuous Integration servers. No matter what is the process there is a need for tools to automate and support the Deployment Pipeline. ![]() Those checkpoints (or steps) could be: Building the software -> Unit testing -> Automated acceptance testing -> Deployment into QA/UAT/Staging environment -> Manual QA -> Release into production.Įxample process diagram for changes moving through the Deployment Pipeline.įor more detailed description of Deployment Pipeline I recommend this article from Continuous Delivery gurus (Jez Humble, David Farley). The process of getting the software from the version control such as Subversion or Git into the end user typically involves traveling through checkpoints. In the simplest way possible explaining Deployment Pipeline I would say that it is an automated way of getting the software from version control into the hand of end user. Deployment Pipeline is a concept of Continuous Delivery.
0 Comments
Leave a Reply. |