Jenkins monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs:
1. Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
2. Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.
Get Jenkins and give it a try to see how useful it can actually be for you!
What's New in This Release:
· ${ITEM_FULLNAME} variable was not working for Maven projects on Windows, so introduced ${ITEM_FULL_NAME} instead. (issue 12251)
· Lock contention issue in build history view. (issue 16831)
· Fixed the HTTP request thread saturation problem with Winstone. (issue 16474)
· Script evaluation script error on IE. (issue 16561)
· surefire-reports not detected for android-maven-plugin (issue 16776)
· maven-failsafe-plugin tests not recognized anymore (issue 16696)
· UI waiting on a queue lock to display cause of queue blockage. (issue 16833)
· UpdateCenter REST API chokes if there was a plugin installation failure. (issue 16836)
· Missing build title in /rssAll when build has no test result. (issue 16770)
· Changed the way matrix axis values are exposed as env variables (issue 11577)
· Maven 3 builds ignored quiet (-q) and debug (-X) options (issue 16843)
· JNLP slave installers can now work transparently with secured Jenkins. (SECURITY-54 / despite the ticket marker, this is not a security vulnerabili...