* Fix two security bugs
Changelog:
Changes in 1.466.2 is unavailable.
What's new in 1.466.1 (2012/07/23)
A current active build in the build history is lost if the job configuration XML uploaded (issue 12318)
UnprotectedRootAction doesn't work for /github-webhook/ (issue 14113)
ERR_CONTENT_DECODING_FAILED returned on testResults and console output after Jenkins reload (issue 13625)
Cannot parse coverage results Premature end of file. (issue 11251)
Changelog:
What's new in 1.447.2 (2012/06/11)
Guice injector failure can cause failure of whole Jenkins (issue 13448)
Jenkins runs out of file descriptors (winstone problem) (issue 9882)
Parsing of POM happens before SNAPSHOT-Parents are updated (issue 8663)
Loading All Build History Fails (issue 13238)
Jenkins is an award-winning application that 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.
This is Long-Term Support Release.
Tested on NetBSD/i386 5.99.58 with apache-tomcat7 and openjdk7.