In this article Kelly Waters describes 7 reasons why we need continuous delivery. For me the most important reason to do this, is to get some control of the product you are building by having continuous integration, sonar, automatic deployment and fitnesse tests!
This enables an agile team to react faster to new changes, features and bugs. Whithout continuous delivery we cannot say anything about our product!
Continuous Delivery is a way to react faster and better to any kind of changes in the product. To have a continuous delivery pipeline we are safer and quicklier, by making the tasks a routine through automation and make it predictable and easier.
A continuous develivery pipeline exist of 5 steps in which they been executed synchronously.
What if we have done al the automation and we have a continuous delivery pipeline?
The benefits are huge to have this, because we can react faster and we can check the quality of our product! Besides al the corporate benefits, from a lazy programmers perspective, it is great to not have to do this kind of stuff manually, so thumbs up ;-)
During this blog i will guide you to creating a continuous delivery pipeline. There are a lot of things to be configured and to setup to make it working. When you are lucky, system management have done setup work, but if not? I have described every step i needed to create this continuous delivery pipeline!
A note, i will not go into details of the technicall stuff i used, this could be done in another blog or search on google. This blog describes only the setup of the pipeline, nothing more!
When you have some questions or comment on the things i have described, please start a discussion!
I hope you enjoy and learn from it!