<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Snehi Pachchigar on Medium]]></title>
        <description><![CDATA[Stories by Snehi Pachchigar on Medium]]></description>
        <link>https://medium.com/@snehipachchigar?source=rss-228c70311d0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pvJ_XTlja9ROcmGEowJb7Q.jpeg</url>
            <title>Stories by Snehi Pachchigar on Medium</title>
            <link>https://medium.com/@snehipachchigar?source=rss-228c70311d0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:01:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@snehipachchigar/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A general CI/CD guideline for deploying your application on the cloud.]]></title>
            <link>https://snehipachchigar.medium.com/a-general-ci-cd-guideline-for-deploying-your-application-on-the-cloud-dc3e08090fe?source=rss-228c70311d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc3e08090fe</guid>
            <category><![CDATA[dc]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-native-application]]></category>
            <category><![CDATA[ci]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Snehi Pachchigar]]></dc:creator>
            <pubDate>Thu, 29 Oct 2020 01:23:24 GMT</pubDate>
            <atom:updated>2020-10-29T01:23:24.650Z</atom:updated>
            <content:encoded><![CDATA[<p>Continuous Integration and Continuous Delivery are one of the fundamental steps in the Software Development Life Cycle in any project. Continuous Integration (CI) enables multiple developers to contribute and collaborate in a shared codespace at a rapid pace. Without an efficient CI, developer collaboration becomes a tedious manual process of coordinating code updates and merges. CI is built on other software development best practices including automated testing, version control, build automation, and automated deployments. Each one of these pillars of continuous integration has its own ecosystem of tools and philosophies.</p><p>Continuous delivery is an approach where teams release quality products frequently and predictably from source code repository to production in an automated fashion. CD focuses an organization on building a streamlined, automated software release process. At the heart of the release process is an iterative feedback loop. The feedback loop revolves around delivery of software to the end user as quickly as possible, learning from their hands-on experience, and then incorporating that feedback into the next release.</p><p>There are many technologies in the market that offer CI/CD solutions. Examples include Github Actions, Circle CI, Azure Pipelines, AWS Code pipelines, Gitlab, bitbucket. All of these has configuration as code in the form of YAML files and are generally paid plans with certain free usage periods or minutes of running pipelines. Jenkins is a legacy CI/CD approach that runs the pipeline using plugins and has a groovy script for configuration.</p><p>Any tool can be used depending on one’s preferences, although, below I have laid a general reference architecture that can be used as a skeletal for reviewing if your internal CI/CD tool or any external tool you use, satisfies the procedure and steps laid below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnfZjKAH5RiBfaH1-9FX2Q.png" /><figcaption>Reference Architecture for an efficient CI/CD</figcaption></figure><p>This is the general architecture for a CI/CD infrastructure that is efficient and has multiple features to handle edge cases for general scenarios.</p><p>This architecture is designed by keeping in mind that the application is a web-hosted application on any modern cloud platform and the CI/CD is for the application code, serving end-users.</p><p>The flow starts as follows. (2) There is a central version control system holding the application code repository. (1) Team of developers, develop and push these features to the repository, on branches other than master.</p><p>(3) Master is the main branch that has restricted rules attached to it. Those can be restricted to prevent force-push/push/merge to master from all fail, except for privileged users.</p><p>As soon as a (3) PR is made on the master branch, a CI step is triggered, which will (4) perform tests on the development code, and improve code — such as (5) lint, prettify or perform some code quality tests.</p><p>This same step is performed if there is a (7) code push on the master branch which is generally approved by a privileged admin developer. (6) After a test has been passed on the PR on the master, the next step is to (9) build the deployment packages. An example of it can be `npm build` or `docker build..` in the case of containers and so on. The build packages are also passed through the testing and scanning phase (10) to check for any vulnerabilities, holes in the build.</p><p>Once the test for build package/image is passed successfully, the next trigger for CD step is to upload it to a package registry (11) which can be a docker registry or npm registry, etc. There will also be a need for credentials to authenticate with the registry. In this case which can be fetched via an external secret manager (12) . All these steps have been going so far for PR deployment.</p><p>For the resource to deploy this code, there is another external (17) Version control system holding Infrastructure as code files (15) . These can be developed by an infrastructure engineer, and this repo holds the IAC scripts for dev, staging and production environments. Initially, along with environment variables from any external config management (14) and secrets from the secrets manager, the resources are deployed on any cloud platform. (The deployment of resources is independent of the change/push in application code. Hence, there is Dev cluster/resources (16) on the cloud which are for checking PR apps. Similarly, a staging environment (21) is deployed on the cloud for the deployment of push events on the master branch. Then, there is this main prod environment (25), spin up the cloud platform.</p><p>Once, the build package tests from the PR are passed, the CD trigger deploys the built code on the dev cluster/ resources (16) and a PR review app can be generated as shown (18) and (20) for developers to play around and check. If there is an issue, the PR is requested to have changes, otherwise, a developer, approves the PR and it is merged in the master branch at (7) .</p><p>Once, it is approved, the latest commit on master goes through the same procedure of testing(4) , build code (9) , test the build (10), and upload the build to a build registry (11).</p><p>Although, as it is a push on the master, the environment this time will be staging, instead of dev, and hence, the CD script/step will be configured to deploy this code to the staging cluster(21) on the cloud. The successful deployment can generate a staging app (22) which can be like ` <a href="https://internal-company-domain.com/">https://internal-company-domain.com</a> `. As this will be analogous to the live production changes, the staging app is passed through more set of testing (23) like load testing, chaos monkey, selenium, other live app testing which are specific to the company. Issues with the tests are again passed down to the issues section in the repository and the code is not deployed for production. Otherwise, if tests pass, the code for deployment to the production environment (24) is approved (generally by a privileged user), and along with the deployment-specific secrets, the code is deployed on the production cluster (25).</p><p>The production cluster is configured to take snapshots at a regular interval and these snapshots are stored in any object storage (27) tool on cloud (like s3). Hence, if everything goes right, the live site is deployed (26) and open for end-user traffic. If there is any issue with the latest production, the previous state can be restored from the snapshot stored.</p><p>There are various tools in the market available for automated CI/CD, but the one that covers these steps above is generally considered a good and efficient CI/CD tool.</p><p>Hope this was helpful! Please share any feedback or queries on snehipachchigar@gmail.com</p><p>Connect with me:<br>- <a href="https://twitter.com/snehi_20">Twitter</a><br>- <a href="https://www.linkedin.com/in/snehi-pachchigar-5aa973102/">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc3e08090fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>