In a nutshell, Jenkins is the leading open-source automation server. Built with Java, it provides over 1000 plugins to support automating virtually anything, so that humans can actually spend their time doing things machines cannot.
Use Jenkins to automate your development workflow so you can focus on work that matters most. It is commonly used for:
- Building projects
- Running tests to detect bugs and other issues as soon as they are introduced
- Static code analysis
Execute repetitive tasks, save time, and optimize your development process with Jenkins.
Jenkins 2.121.1 has been released.
Changes since 2.121:
- Faster list rendering of Plugin Manager » Available. (issue 51205)
Notable changes since 2.107.3:
- Install from java.sun.com installation method for JDK tools has been moved to a new JDK Tool Plugin. (issue 22367)
- It is no longer possible to rename jobs from their configuration page. Jobs now have a link in the side panel titled “Rename” that links to a page specifically dedicated to renaming jobs. (issue 22936)
- The Job/Build permission no longer implies the Job/Cancel permission. The latter needs to be granted explicitly to users who previously got it via this relationship. (issue 14713)
- Update Remoting from 3.17 to 3.20 in order to apply various performance and diagnosability improvements, such as logging warnings when anonymous classes are serialized over a Remoting channel, and allowing Jenkins core to always deserialize exceptions even if they’re not whitelisted. To benefit from the latter improvement, Remoting needs to be updated on the agent side as well. (full changelog)
- Fix issue preventing process killing vetoes being effective on agents. (issue 9104,
ProcessKillingVetoextension point implementations)