https://aripd.com/tags/automation/ Recent content in Automation on ARI Systems Hugo en-us ARI Systems Sat, 16 May 2026 06:19:44 +0000 https://aripd.com/blog/ci-cd/ Tue, 28 Jul 2020 00:00:00 +0000 https://aripd.com/blog/ci-cd/ <h2 id="references">References <a href="#references" class="permalink"><i class="bi bi-link-45deg"></i></a></h2><ul> <li><a href="https://bitbucket.org/atlassian/workspace/projects/BPP" target="_blank" rel="noopener noreferrer">Bitbucket Pipelines Pipes</a></li> <li><a href="https://itnext.io/using-bitbucket-pipelines-to-create-a-docker-image-ad40b99d4969" target="_blank" rel="noopener noreferrer">Using Bitbucket Pipelines to create a Docker image</a></li> </ul> <h2 id="what-is-continuous-integration-continuous-delivery-continuous-deployment">What is Continuous Integration, Continuous Delivery, Continuous Deployment? <a href="#what-is-continuous-integration-continuous-delivery-continuous-deployment" class="permalink"><i class="bi bi-link-45deg"></i></a></h2><p><img src="./CI-CD-pipeline.webp" alt="CI-CD Pipeline" title="CI-CD Pipeline" class="img-fluid" loading="lazy" /></p> <h3 id="continuous-integration">Continuous Integration <a href="#continuous-integration" class="permalink"><i class="bi bi-link-45deg"></i></a></h3><p>Developers practicing continuous integration merge their changes back to the main branch as often as possible. The developer&rsquo;s changes are validated by creating a build and running automated tests against the build. By doing so, you avoid the integration hell that usually happens when people wait for release day to merge their changes into the release branch.</p>