The software development principle of continuous delivery is a team effort to create and maintain an automated building, testing and deployment of code and software.
Using continuous delivery guarantees that software is released long before users are given access to it and that additional releases occur very frequently – not less than once per iteration but normally as often as several times a day. Software is continuously tested for functionality Continue reading “The Continuous Delivery Pipeline” »
Continuous integration is a team software development and management principle that can be applied to any iterative programming model. It was supposedly developed in the early 60′s when IBM’s team developing OS/360 had to re-build the codebase four times a day. Recently, continuous integration become more popular boosted by the need to build high-quality, high-performance and reliable software quickly.
There are a few principles that characterize best practices of continuous integration such as committing new code frequently (at least once a day), categorizing developer tests, developing and using a steadfast integration build server that gives continuous feedback mechanism and the staging builds. Continue reading “Continuous Integration – Quality on the Fast Track” »
Continuous deployment is a process by which software is updated and released numerous times during one day. The principle of continuous deployment is founded on the process of continuous integration which means that after a successful build and automated testing of the updated code, modifications are routinely pushed to production. While the continuous deployment process suggests continuous delivery the contrary isn’t necessarily true. Continue reading “Continuous Deployment” »
Continuous delivery is a software development strategy to optimize and speed-up deployment and delivery of high-quality software by using smart automation. This automation process comprises all parts of the development process from defining the requirements to deployment to product release. Compared with traditional delivery lifecycles that have a relatively long delivery procress (Agile: 2-3 weeks, Waterfall: up to years), continuous delivery prioritizes the rapid integration of new ideas that are continually released Continue reading “Continuous Delivery” »