Getting a continuous delivery model right needs more than a structured way of handling development. It also needs the appropriate tools for managing test and build.
That’s where the Jenkins continuous integration server comes in. It works with your choice of source control, your test harnesses, and your build server. It’s a flexible tool, initially designed for working with Java, but has now been extended to support Web and mobile development and even to build Windows applications.
Jenkins is perhaps best thought of as a switching network for shunting files through a test-and-build process. It responds to signals from the various tools you’re using -- thanks to a library of more than 1,000 plug-ins. These include tools for integrating Jenkins with both local Git instances and the cloud GitHub service, allowing you to extend a Gitflow continuous development model into your build and delivery processes.
To continue reading this article register now