Continous Integration & Delivery

Description

OVERVIEW OF CONTINOUS INTEGRATION & DELIVERY

to know more about countinous integration & delivery

          CI act as a safety net that let developer prevent many issues before they reach user. As a result, developers ship code with more confidence, but not necessarily faster — the deployment process may still be manual, long, and error-prone.The best initial investment developers can make is to ensure that their automated test suite is comprehensive and stable enough that they feel safe to deploy every passed CI build to a staging, and later production environment, without a long manual QA (quality assurance) processes.we strongly believe that developers must get CI results within 10 minutes, otherwise their productivity shrinks due to lack of focus and frequent context switching.

Continuous Delivery (CD) is a practice of automating the entire software release process. The idea is to do CI, plus automatically prepare and track a release to production. The desired outcome is that anyone with sufficient privileges to deploy a new release can do so at any time in one or a few clicks. By eliminating nearly all manual tasks, developers become more productive.

CD is a step up from Continuous Delivery in which every change in the source code is deployed to production automatically, without explicit approval from a developer. A developer’s job typically ends at reviewing a pull request from a teammate and merging it to the master branch. A CI/CD service takes over from there by running all test and deploying the code to production, while keeping the team informed about outcome of every important event.