|Initial release||2 February 2011|
2.23 / 18 September 2016
Jenkins helps automating the non-human part of the whole software development process, with now common things like Continuous Integration, but by further empowering teams to implement the technical part of a Continuous Delivery. It is a server-based system running in a servlet container such as Apache Tomcat. It supports SCM tools including AccuRev, CVS, Subversion, Git, Mercurial, Perforce, Clearcase and RTC, and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands. The creator of Jenkins is Kohsuke Kawaguchi. Released under the MIT License, Jenkins is free software.
Builds can be triggered by various means, for example by commit in a version control system, by scheduling via a cron-like mechanism and by requesting a specific build URL. It can also be triggered after the other builds in the queue have completed.
One of the biggest technical strengths of Jenkins is that it is extremely extensible. This, plus the desire to be very welcoming as a community, is the reason why Jenkins has now more than 1200 plugins and hundreds of developers, and that several new ones are created and made available in the official Update Center each month.
Around 2007 Hudson became known as a better alternative to CruiseControl and other open-source build-servers. At the JavaOne conference in May 2008 the software won the Duke's Choice Award in the Developer Solutions category.
During November 2010, an issue arose in the Hudson community with respect to the infrastructure used, which grew to encompass questions over the stewardship and control by Oracle. Negotiations between the principal project contributors and Oracle took place, and although there were many areas of agreement a key sticking point was the trademarked name "Hudson", after Oracle claimed the right to the name and applied for a trademark in December 2010. As a result, on January 11, 2011, a call for votes was made to change the project name from "Hudson" to "Jenkins". The proposal was overwhelmingly approved by community vote on January 29, 2011, creating the Jenkins project.
On February 1, 2011, Oracle said that they intended to continue development of Hudson, and considered Jenkins a fork rather than a rename. Jenkins and Hudson therefore continue as two independent projects, each claiming the other is the fork. As of December 2013, the Jenkins organisation on GitHub had 567 project members and around 1,100 public repositories, compared with Hudson's 32 project members and 17 public repositories.
On April 20, 2016 version 2 was released with the Pipeline plugin enabled by default. The plugin allows for writing build instructions in Apache Groovy.
How it works
Located at a server where the project's main build is created, Jenkins triggers a new build every time a user checks in some changes into the source code, thus supporting the process of continuous integration for testing or development phases. The builds created are reflected on the Jenkins dashboard, with details logged in such as time and date created, build status such as success or failure, error messages in case of build failure, reports and other helpful details which helps the user keep track of the builds generated. Jenkins can be configured to be more user friendly by customizing it to send notifications when the build is generated. As it supports more than one projects, while a build is already in progress, a build queue is created according to the time-stamp with which each build is triggered.
Distributed builds are supported to reduce the load off of the central server, mostly used in case of large builds coupled with heavy trigger frequency.
Installation and Configuration
Jenkins can be run as services by installing them directly on the operating systems or alternatively by deploying Jenkins .war file in any container (such as Apache Tomcat) that supports Servlet version 3.1 and JSP 2.0., which in turn will run as a service. Originally Jenkins was created to work on Unix/Linux based systems only, because of which it supports native integration with the operating systems such as Ubuntu, RedHat and Docker. Windows support was added later.
Jenkins demands sufficient storage capacity wherever it is hosted as all the builds generated are accommodated with Jenkins.
Jenkins UI portal provides various configuration options under Manage Jenkins option where users can add/download plugins, security settings, credentials, reload configurations from disk, notifications etc.
Plugins have been released for Jenkins that extend its use to projects written in languages other than Java. Plugins are available for integrating Jenkins with most version control systems and big databases. Many build tools are supported via their respective plugins. Plugins can also change the way Jenkins looks or add new functionality. There are a set of plugins dedicated for the purpose of unit testing that generate test reports in various formats (for example JUnit bundled with Jenkins, MSTest, NUnit etc.) and automated testing which supports automated tests. Builds can generate test reports in various formats supported by plugins (JUnit support is currently bundled) and Jenkins can display the reports and generate trends and render them in the GUI.
Jenkins' security depends on two factors, access control and protection from external threats. Access control can be customized via two ways, user authentication and authorization. Protection from external threats such as CSRF attacks and malicious builds is supported as well.
There are similar tools for other programming frameworks such as:
See continuous integration for more.
Awards and Recognition
- InfoWorld Bossie Award (Best of Open Source Software Award) in 2011.
- Received Geek Choice Award in 2014.
- Jenkins 1.396 released, The first release of Jenkins is posted, Kohsuke Kawaguchi
- Dan Dyer. "Why are you still not using Hudson?". Retrieved 2008-05-21.
- Kawaguchi, Kohsuke; et al. "Use Hudson: License". Retrieved January 30, 2011.
- Kawaguchi, Kohsuke. "Hudson" (PDF). Retrieved 28 June 2013.
- "Plugins - Jenkins - Jenkins Wiki".
- "Securing Jenkins". jenkins.io. Retrieved 2016-09-13.
- "Buildbot". buildbot.net. Retrieved 2016-09-23.
- "Welcome to the tox automation project — tox 2.4.0.dev1 documentation". tox.readthedocs.io. Retrieved 2016-09-23.
- "Travis CI - Test and Deploy with Confidence". travis-ci.com. Retrieved 2016-09-23.
- "Continuous Integration and Deployment service for Windows developers". AppVeyor. Retrieved 2016-09-23.
- "Jenkins – Django". code.djangoproject.com. Retrieved 2016-09-23.
- "Awards - Jenkins - Jenkins Wiki". wiki.jenkins-ci.org. Retrieved 2016-09-13.
|MediaWiki has documentation related to: Jenkins|
- "Jenkins homepage". Retrieved 2016-03-03.
- Moser, Manfred; O'Brien, Tim (2011-11-25). Hudson free book (PDF). Oracle, Inc.
- Kohsuke Kawaguchi (2011-02-08). "Jenkins creator Kohsuke Kawaguchi on The Changelog podcast talking about the project origin and name change". the changelog. Retrieved 2016-03-03.
- Kohsuke Kawaguchi (2015-02-15). "7 Ways to Optimize Jenkins/Hudson (by its founder)" (PDF). CloudBees. Retrieved 2016-03-03.