I added a mode where one can launch a child process without the built-in pumping support, making it trivial to read until EOF in the distributed environments.
This concludes the fix.
I did a checkout for our internal fork of JmDNS [1] and the
upstream version [2] to compare what the differences were..
I found none. There do not appear to be any local edits to
our fork so I can not figure out why we did the fork to
begin with.
Perhaps some older version had locally patched bugs which
have since been resolved? Anyhow, given that JENKINS-8647
is causing lots of people lots of grief, and it is enabled
by default, I went ahead and bumped to jmdns-3.4.0 upstream.
I think reduction of forks for library projects is generally
good, and especially when we have no practical changes made
to our version.
[1] https://github.com/jenkinsci/jmdns
[2] https://jmdns.svn.sourceforge.net/svnroot/jmdns/tags/JmDNS_3_2_1/
* commit 'b7a6c5d5d18ac4a00781919788e5c57360f05529':
Reverting the BUIlD_TAG change.
Fixed BUILD_TAG env var to not say hudson and added JENKINS_* versions of more env vars.
Conflicts:
changelog.html
hudson.UDPBroadcastThread#testMulticast hangs when the network isn't enabled on my Linux box: joinGroup throws IOException and the ready lock isn't released.
This ready lock is only used in the tests.
* JENKINS-4756:
minor touch up
FIXED JENKINS-4756 the executor number was not always unique. Computer.executors.size() does not provide a unique number within one Computer.
HUDSON-8401.
This grouping of tests targets all Sunday to *another day of week* cron
tabs. There are likely other pairs that could be tested, but this seemed to
work out most of the bugs.
After thinking about it, I don't want to deal with hudsonslave here. jenkinsslave should be found anyway, so that code path should not have been triggered.
And cleaning up residual services isn't jenkins job. Otherwise both can't coexist.
After thinking about it, I don't want to deal with hudsonslave here. jenkinsslave should be found anyway, so that code path should not have been triggered.
And cleaning up residual services isn't jenkins job. Otherwise both can't coexist.
Persist a user-requested offline status for a slave across
restarts. Previously slaves would come back online if the server
was restarted while they were marked 'temporarily offline'.
I believe this also addresses JENKINS-7934 and JENKINS-7805
which look like duplicates.
First pass at making sure we don't stop copying when the reader reads 0 characters.
I will now also review the callers for our internal code, and check if we can use IOUtils methods instead.