anchor.diff:  
   Usually, CD pipelines are set up so that the parts which provide fast feedback run first. In practice, quick-running unit tests are usually run earlier in the pipeline than the slower-running functional and performance tests. This ensures quicker feedback by making sure that slower running tests aren’t run unnecessarily taking up resources.
   
  -<%= image_tag 'blog/importance-cd-pipelines/Fast-Feedback-First.png', :alt => 'Fast Feedback First', :title => 'Fast Feedback First' %>
  +<%= image_tag 'blog/importance-cd-pipelines/Fast-Feedback-First.png', :alt => 'Fast Feedback Loop', :title => 'Fast Feedback First' %>
   
   ### 2. Most important feedback first {#principle-important-feedback}
   
  
positive.code: 
  This is one of the bedrock CD principles - the ability to build once, get an artifact and run it through different kinds of tests, so that your confidence in that specific artifact increases over time. Once it goes through the final gate in the CD pipeline successfully, you can be assured that the artifact is safe to be deployed to production and used.
  
  <%= image_tag 'blog/importance-cd-pipelines/build-reuse.jpeg', :alt => 'Build once and reuse', :title => 'Build once and reuse' %>
  
  It is up to the CD pipeline solution you choose to provide a good artifact propagation mechanism, so that, even with multiple instances of the pipeline running, it keeps track of the correct version of the artifact to be used in the rest of the pipeline.
  
  
negative.code: author: Aravind S.V, Product Manager at GoCD
  excerpt: "The path from commit to production involves numerous moving parts, (like multiple code and asset repositories, automatic and manual handoffs, unit tests, integration tests, acceptance tests, performance tests, security tests, etc.) and time that it takes to execute all of these elements. You need a way of modeling your workflow so that people can see, understand and talk about it. This is where CD pipelines come in."
  title_tag_of_header: "Importance and Principles of CD Pipelines | GoCD Blog"
  meta_description: "You need a way of modeling your workflow so that people can see, understand and talk about it. This is where CD pipelines come in."
  meta_keywords: "GoCD, continuous delivery, deployment pipelines, snap ci, open source, continuous delivery tool"
  summary_image: "/assets/images/blog/importance-cd-pipelines/importance_pipelines_hero.jpg"
  tags: Modeling Deployment Pipelines
  ---
  ### In an ideal, magical world, your end-to-end deployment from a commit to production looks like this:
  
  <%= image_tag 'blog/importance-cd-pipelines/magic.jpeg', :alt => 'Magic Deployment Pipeline', :title => 'Magical Deployment Process' %>
  
  If this represents your situation (especially if all your tests run quickly enough that you’re confident about deploying to production), you don’t really need a good Continuous Delivery (referred to as CD) solution and you can stop reading this post right here.
  
  