{"id":27346,"date":"2019-07-09T07:29:23","date_gmt":"2019-07-09T11:29:23","guid":{"rendered":"https:\/\/centricconsulting.com\/?p=27346"},"modified":"2021-12-15T00:16:32","modified_gmt":"2021-12-15T05:16:32","slug":"devops-pipelines-part-2-taking-a-look-at-continuous-delivery-and-testing","status":"publish","type":"post","link":"https:\/\/centricconsulting.com\/blog\/devops-pipelines-part-2-taking-a-look-at-continuous-delivery-and-testing\/","title":{"rendered":"DevOps Pipelines Part 2: Taking a Look at Continuous Delivery and Testing"},"content":{"rendered":"
We talked about Release Planning (RP) and Continuous Integration (CI) in part one<\/a> of this series.\u00a0Those two capabilities aid in story creation and agile software development.<\/p>\n Now, I want to talk about Continuous Delivery (CD) and Continuous Testing (CT). This part is where we get into more automation.<\/p>\n <\/a>Continuous Delivery (CD) is a bit complex these days. In the past, as companies requisitioned \u201cstatic\u201d servers from the IT team, potentially delaying completing provisioning step for weeks.<\/p>\n For example, you might write a \u201cDeployment\u201d with Chef recipes to deploy packages to the provisioned server. However, due to the proliferation of cloud computing, the provisioning of environments takes on a new meaning.<\/p>\n Infrastructure as Code (IaC) is now more commonplace in organizations. Having stories around configuration management as well as IaC is critical for the Configuration or Provision Epic<\/strong>. If you modernize your infrastructure architecture, using containerization is the next step for the Package or Deploy Epic. It\u2019s important to have stories around docker or serverless technology, like Lambda<\/a>.<\/p>\n Automatic recognition of the completion of a step that immediately triggers the next step speeds up your pipeline. The CI Engine controls this process.\u00a0\u00a0<\/strong><\/p>\n <\/p>\n The chart below explains:<\/strong><\/p>\nContinuous Delivery<\/h2>\n