[FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor()
[FIXED JENKINS-24014] Make reverse proxy check tolerate ?auto_refresh
Merge pull request #1348 from daniel-beck/JENKINS-20307

[FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor()
Merge pull request #1373 from daniel-beck/JENKINS-24014

[FIXED JENKINS-24014] Make reverse proxy check tolerate ?auto_refresh
Noting #1348, #1373
[FIXED JENKINS-21977] Skip HsErrPidList when running functional tests.
Fixing dir listing in test to not be case sensitive (related to JENKINS-24317)
[FIXED JENKINS-23724]
For some reason IE10 craches when document.getElementsByName is called and there is an element with a name attribute but no value. In this case a button had a name attribute set with an empty string as the value.
Noting change to logging in Stapler
[JENKINS-24317] Amending 80f78d573267b69a0bf3e7cbb2f7b4741974d94d.
If we are running on a case-insensitive FS, the test makes no sense because migration would never even be attempted to begin with.
Another attempt to diagnose a random test failure. (Cf. #1370.)
[FIXED JENKINS-23522] Defend against stack overflows when a listener (unnecessarily) called super from a deprecated method.
Fixes #1295 a little differently.
NPE diagnosis from ProjectTest.testCheckout.
java.lang.NullPointerException: null
	at hudson.model.AbstractBuild.setWorkspace(AbstractBuild.java:296)
	at hudson.model.ProjectTest.testCheckout(ProjectTest.java:423)
[FIXED JENKINS-24514]

Ubuntu (at least as of 12.04) has the default umask 022, which made some
users nervous. Quoting its /etc/login.defs below, which explains its
historical origin:

  UMASK is the default umask value for pam_umask and is used by
  useradd and newusers to set the mode of the new home directories.
  022 is the "historical" value in Debian for UMASK
  027, or even 077, could be considered better for privacy
  There is no One True Answer here : each sysadmin must make up his/her
  mind.

It does seem to me that a bit more restrictive default is sensible,
so this change introduces /etc/default/jenkins parameter that sets the
default umask to 027 to prevent "others" from seeing files.

Not that keys and other sensitive files are protected anyway, so it is
not the case that the privacy of Jenkins data files have been vulnerable
prior to this change.
Integrated the latest version with a better error diagnostics
Merge commit '52c28ae38d29773e2a47db3f9dfaa57291e0ee87'
[maven-release-plugin] prepare release jenkins-1.578
[maven-release-plugin] prepare for next development iteration
updated changelog for release
updated changelog as a part of the release