Don't let the partially loaded Jenkins cause a possible data loss.

At some point after this code was originally written, I/O in remoting
became asynchronous. So we need to sync with that before we swap out
the new log output stream, or else you cut off stuff at the wrong
moment.

Normally the command transfer in remoting is slow enough that
you get more or less synchronized output anyway, which is why
this poblem remained unnoticed.

But if the uncliamed buffer gets large, write operation will take a long
time, which makes this issue more likely to show up.

This fix address this problem by doing a proper sync.
The recycling of ByteArrayOutputStream is also disabled because it makes
synchronization tricky.

configurations in the matrix.

This reverts commit e38e687d.

come back online when disk space becomes available.

Use /var/cache/jenkins to hold the unpacked jenkins.war file at runtime.

Increase stop timeout from 5 to 20 seconds.

resizable

Use YUI resize method to add resize handle for build timeline widget.

Use window.attachEvent if window.addEventListener is not supported.

see https://groups.google.com/forum/#!topic/jenkinsci-ja/4FsDhryOwYE

[FIXED JENKINS-11073] handle failure to set timestamp on Windows platforms more gracefully - this time hopefully for real