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:
· Reverted change in 1.500 causing serious regression in HTTPS reverse proxy setups. (issue 16368)
· Getting test results from custom test mojos failed build. (issue 16573)
· Restored Java 5 compatibility. (issue 16554)
· Bogus “Build Record Root Directory” inadequately diagnosed. (issue 16457)
· Plugin icons in the sidebar were not being properly cached. (issue 16530)
· Broadly as well as deeply nested build causes overwhelmed the UI after 1.482. (issue 15747)
· API typo DependecyDeclarer corrected.
· Avoid eagerly loading builds in Changes in dependency or culprit list. (pull 689)
· Run parameters do not support folders. (issue 16462)
· Fixed RememberMe cookie signature generation. (issue 16278)
· Fixed NullPointerException when copying from existing Maven job (issue 16499)