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:
· Exception in flyweight tasks when checking if an executor is interrupted. (issue 17025)
· JNA-related linkage errors on Windows not handled gracefully. (issue 15466)
· Added run display name as an environment variable when RunParameter is used (pull 720)
· Fixed "Manage" sub-contextmenu for non-standalone deployments (pull 721)
· Absolute URLs in console output (issue 16368)
· Revert ampersand encoding which can cause backward incompatibility issue (pull 683)
· Fix dependency graph computation when upstream build trigger is involved (issue 13502)
· Disabled Authenticode verification for Windows services. (issue 15596)