ahochsteger asks 'why do we mess with file permissions anyway?' and he's
right! I digged the history but couldn't find why we do it.
I think we should just set the permissions of the top-level directories,
but leave the other file permissions as-is.
In addition,
- I see no point in touching usr/bin usr/sbin.
perhaps C&P mistake from some samples?
- Don't touch /var/lib/hudson if .for-jenkins is present,
so that people using the hudson user can keep upgrading new
versions of jenkins and run it as hudson
- /var/run/hudson contains no important information,
so no need to bring it over to /var/run/jenkins
The ManagedWindowsServiceLauncher refers to hudson.exe and hudson-slave.exe while we renamed the artifact to jenkins.exe.
Tentative fix, completely untested (no windows box around).
Not sure about the service name (jenkinsslave). I added a second check for backward compatibility but I have no idea if it's useful.
loadAllBuildHistory() fails to set the headers field on the replacement buildHistory DOM element.
The patch fixes the problem by recreating a headers field.
It also:
* slightly refactor the loadAllBuildHistory() method for readability
* add a FIXME note that the server side history widget should fail if the n parameter is missing.
* add a pre-condition check to the buildHistory() update to catch potential bugs (note that the logging is disabled as Yahoo.log doesn't appear available)
The ManagedWindowsServiceLauncher refers to hudson.exe and hudson-slave.exe while we renamed the artifact to jenkins.exe.
Tentative fix, completely untested (no windows box around).
Not sure about the service name (jenkinsslave). I added a second check for backward compatibility but I have no idea if it's useful.
loadAllBuildHistory() fails to set the headers field on the replacement buildHistory DOM element.
The patch fixes the problem by recreating a headers field.
It also:
* slightly refactor the loadAllBuildHistory() method for readability
* add a FIXME note that the server side history widget should fail if the n parameter is missing.
* add a pre-condition check to the buildHistory() update to catch potential bugs (note that the logging is disabled as Yahoo.log doesn't appear available)
Diverging from the normal RC process since the additional commits have
alrady been made in the master.
* rc:
preparing for RC
bug fix in the test
Fixed a bug in the test harness.
... so as to follow the convention of keeping the master branch open for
commits.
* after-first-release:
noting the changes
Other languages on JVM may not be able to provide the type information.
Added autocomplete feature to BuildTrigger