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:
· Can't build using maven 3.1.0 (issue 15935)
· Fixed Winstone+mod_proxy_ajp+SSL combo issue. (issue 5753)
· JENKINS_DEBUG_LEVEL misinterpreted by Winstone, causing excessive logging. (issue 18701)
· Since 1.520, Jenkins requires Java 6 or later, breaking Maven builds set to use JDK 5. Now falls back to JVM of slave agent but sets compile/test flags to use defined JDK. (issue 18403)
· Since 1.517, Maven projects using Maven 2 could not build projects using extensions depending on Apache Commons Codec. (issue 18178)
· Test harness was packing copies of Maven into plugin archives under some conditions. (issue 18918)
· Provided maven settings.xml in maven builder is lost. (issue 15976)
· Exception when running polling with a Maven installation not defined on master. (issue 18898)
· Since 1.477 GET on /view/…/config.xml included a spurious wrapper element. (issue 17302)
· Clearer display of log messages: chronological order, and coloration of repeated vs. fresh metadata (date, log level, log source...