Jenkins and Continuous Integration
Jenkins has emerged as one of the leading Continuous Delivery platforms. Continuous Delivery means that the processes of writing, testing, building and delivering code do not occur in distinct stages at fixed intervals. Instead, these processes are continually in sync with one another, and they occur on an ongoing basis.
The idea behind Continuous Integration is to make software production more efficient by eliminating the barriers between different teams. Jenkins facilitates this goal by allowing users to write "pipe lines" using software scripts, which automate the Continuous Delivery process.
For VARs, Continuous Integration means that users now expect software to be released earlier and more often than ever, without compromising on quality. The era when you could get away with updating your products once ever few years is over.
Jenkins has emerged as one of the leading Continuous Delivery platforms. Continuous Delivery means that the processes of writing, testing, building and delivering code do not occur in distinct stages at fixed intervals. Instead, these processes are continually in sync with one another, and they occur on an ongoing basis.
The idea behind Continuous Integration is to make software production more efficient by eliminating the barriers between different teams. Jenkins facilitates this goal by allowing users to write "pipe lines" using software scripts, which automate the Continuous Delivery process.
For VARs, Continuous Integration means that users now expect software to be released earlier and more often than ever, without compromising on quality. The era when you could get away with updating your products once ever few years is over.
