Ssh – jenkins cli build via ssh is disconecting after 10 minutes

Jenkinskeepalivessh

I have two jenkins instances. I want job at 1st instance to invoke job at 2nd instance, wait until it ends and perform some actions (using artifacts produced by job @ 2nd)

I've come up with this solution – using Jenkins CLI commands via SSH

ssh -p 2222 second-jenkins build second-job -s -v <further options>

But this session disconnects after 10minutes with message:

Received disconnect from 192.168.147.102: 2: User idle has timed out
after 600000ms.

I found ssh client option named ServerAliveInterval

ssh -o ServerAliveInterval=30 -p 2222 second-jenkins build second-job -s -v <...>

Documentation for this option says

ServerAliveInterval

Sets a timeout interval in seconds after which if no data has
been received from the server, ssh(1) will send a message through
the encrypted channel to request a response from the server. The
default is 0, indicating that these messages will not be sent to
the server. This option applies to protocol version 2 only.

This works but only when server is quiet by at least 30 seconds within every 10 minutes. Of course I can use 1 second instead 30, but it wont work for jobs with continous console output (eg. maven builds).

Is there solution which keep connection alive even for hevy console output jobs?

Best Answer

Add this to Jenkins startup to disable the SSHD timeout:

-Dorg.jenkinsci.main.modules.sshd.SSHD.idle-timeout=0

See also https://blog.redaalaoui.me/blog/jenkins-cli-ssh-timeout/

Related Solutions

How to get Jenkins to execute a script that it pulled from Git

For my build (on a Linux host), I do something like this (as a build step in Jenkins) to execute a build script out of the freshly-checked-out workspace:

Execute shell Command:

 sh -x $WORKSPACE/build/myproject.build

I presume it would work similar on Windows, except of course you would use \ rather than / and you're using python rather than sh to execute your script.

Maven interfering with Jenkins post build script

Finally figured it out! I'm using a Maven plugin to extract the module version via a Maven plugin, based on this SO article.

The command produces output like this

[INFO] --- maven-help-plugin:2.1.1:evaluate (default-cli) @ master-parent ---
[INFO] No artifact parameter specified, using 'com.myorg:master-parent:pom:0.3.02' as project.
[INFO] 
0.3.02
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]

My initial BASH call to extract the version number

version_override=$(mvn org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate -Dexpression=project.version | grep -v '[INFO]')

However, every so often (and yet unsure where to control this), Maven will reach out for updates to modules (I think). This is where the spurious Downloading output comes from, which mucks with my assignment from above.

I've now revised the command as follows

version_override=$(mvn org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate -Dexpression=project.version | egrep -v '[INFO]|Downloading:' | tr -d ' \n')

Likely still not bullet proof though, who knows what other output could come from this command, for example some day instead of leading [INFO] lines, maybe it spits out [ERROR] or something...

Anyway, it's tightened down for the time being. I really did think this was a Jenkins/Maven issue at first, but turns out it was just a BASH scripting issue!

Related Topic