Retries in ConnectionCheckSSH
See original GitHub issueIn the execute method of ConnectionCheckSSH, there is a line of code as follow:
final int retries = Math.min(0, parent.retries);
That causes the number of retries to be always 0 (unless the parent.retries is negative). The result is that when the plugin starts a Docker container and then attempts to connect to it, the error “java.io.IOException: SSH service hadn’t started after 0 seconds.” will often be encountered.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
PortUtils.ConnectionCheckSSH (Docker plugin 1.2.10 API)
Tests the SSH connection. If the parent PortUtils.ConnectionCheck.withRetries(int) was set to more than zero then more than one attempt will be made, ...
Read more >PortUtils.java example - Javatips.net
getPort()); } public static class ConnectionCheck { private final String host; private final int port; private int retries = 10; private long retryDelay ......
Read more >hudson.slaves.ComputerLauncher Java Examples
ConnectionCheckSSH connectionCheckSSH = connectionCheck. ... + "Try increasing the number of retries (currently " + maxNumRetriesOrNull + ") and/or the ...
Read more >jenkinsci - Bountysource
If Jenkins fails to launch a container say due to a SSH error, it'll keep retrying until it exhausts the container cap value....
Read more >Index (Docker plugin 1.2.9 API) - Jenkins Javadoc
ConnectionCheckSSH - Class in com.nirima.jenkins.plugins.docker.utils ... Sets the number of retries, such that PortUtils.ConnectionCheck.execute() will try ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

“oops” Yes, that looks like a bit of an oversight on my part. …and that code had
noa faulty unit-test so this one slipped through.I’ll fix it.
OK, thanks for confirming the fix. I’ve merged the code changes into master and this will be fixed in the next release.