- 22 4月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 17 4月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 15 4月, 2013 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 07 4月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 02 4月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 26 3月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 25 3月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 23 3月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 22 3月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Fixed the throughput problem between master/slave communication. This fix contains two independent problems. One was in the remoting. During a large sustained data transfer (such as artifact archiving and large test reports), the way we were doing flow control and ACK-ing were penalizing us badly. I improved the flow control algorithm in remoting 1.23, and also increased advertised window size so that the transfer can saturate available bandwidth even when a latency is large. (And unless the reader side is excessivesly slow, this shouldn't increase any memory consumption.) The other fix was in trilead-ssh2, which is our SSH client implementation used by ssh-slaves plugin. The buffer size for flow control was too small. I improved the way buffering is done to reduce the memory footprint when the reader closely follows the writer, then I increased the advertised window size. Again, this shouldn't increase memory consumption (in fact it'll likely actually reduce them) unless the reader end gets abandoned. On my simulated latency-injected network, the sustained transfer rate is now on par with scp. We win for smaller files because of the TCP slow start penality that scp would incur, and we lose a bit as files get larger due to additional framing overhead. If you have manually extracted slave.jar and placed them on slaves, you need to update them to 2.23 to see the performance benefits.
-
- 18 3月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 11 3月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 07 3月, 2013 1 次提交
-
-
由 Jesse Glick 提交于
[FIXED JENKINS-16474] Winstone and executable WAR upgraded to actually support --httpKeepAliveTimeout.
-
- 04 3月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 02 3月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Disable authenticode verification on jenkins.exe and jenkins-slave.exe by generating a proper application configuration file. See: http://msdn.microsoft.com/en-us/library/cc656914.aspx See: http://msdn.microsoft.com/en-us/library/bb629393.aspx See: http://support.microsoft.com/kb/936707
-
- 01 3月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
This helps us catch a typical error of not using ${rootURL} or getContextPath() where needed.
-
- 27 2月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 26 2月, 2013 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 17 2月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 16 2月, 2013 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 14 2月, 2013 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Fixed the HTTP request thread saturation problem with Winstone. (cherry picked from commit 4b1a95f2) Conflicts: changelog.html
-
由 Kohsuke Kawaguchi 提交于
- Use the proper block cipher mode. Or else the information about the plain text still ends up revealing as a pattern without the attacker knowing the key. - No need to hide SLAVE_SECRET from the encrypted payload. jnlpMac is needed to decrypt this payload to begin with, so there's no point in hiding it. This simplifies the code a little bit. - Using a newer slave installer that uses the -secret option (cherry picked from commit f4496df1)
-