Introduction to Jenkins!
Jenkins is one of the most popular open-source continuous integration and continuous delivery servers available today. It began as a product called Hudson, developed at Sun Microsystems in 2004-2005, before it was forked from Hudson and renamed Jenkins in 2011, as the result of a dispute between the Hudson community and Oracle. Kohsuke Kawaguchi, the creator of Hudson/Jenkins became the Chief Technical Officer for Cloudbees in 2014 and Cloudbees now commercially offers Jenkins as a cloud solution.
The most important thing about Jenkins is not necessarily the software, but rather the community that has rallied around Jenkins and built out hundreds of plugins to accomplish almost anything that you would want to do. Jenkins provides support for all popular source code management (SCM) systems, including Git, Subversion, Mercurial, and CVS, popular build tools like Maven, Ant, Gulp, and Grunt, as well as testing frameworks and report generators. Jenkins plugins provide strong support for technologies like Docker and ECS, which enable the creation and deployment of cloud-based microservice environments, both for testing as well as production deployments. And, in 2016, Jenkins released powerful delivery pipeline support using a Groovy Domain Specific Language (DSL) in what they refer to as “Pipeline as Code”.
In short, Jenkins provides all of the features and functionality that you need to build a robust continuous integration and continuous delivery pipeline. Throughout this series of articles we will explore different facets of Jenkins and configure it to run our builds, setup test environments, and even push applications from the SCM to production.
Read the entire article here, Introduction to Jenkins
via the fine folks at VMTurbo!