Saturday, April 2, 2016


Continuous Integration:(CI)
CI is a development practice that requires developers to integrate code into a shared repository(SVN/Clearcase/GIT) several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.

Continuous Delivery:
Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. You're doing continuous delivery when: Your software is deployable throughout its life cycle.

Continuous Deployment:
Continuous deployment is the next step past continuous delivery, where you are not just steadily creating a deployable package, but you are actually deploying it steadily

Continuous Deployment is also consistently deploying code to production as features are completed, and as soon as you have met the release criteria for those features. That release criteria depends on your situation, and may be running some automated tests, code reviews, load tests, manual verification by a QA person or business stakeholder, or just having another pair of eyes look at your feature and make sure it doesn't explode. Again, the specific criteria can vary, but the key idea is to have a steadily flowing pipeline pushing changes to production, always moving the code forward, and keeping the pipeline as short as realistically possible.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.