markewaite Thanks for the pointer, I used https://github.com/jerrykuch/ersatz-setsid to run a JNLP agent on macOS using setsid and am no longer seeing errors on macOS using a credential of type 'SSH Username w/ Private Key' in Jenkins.

dnusbaum there is a setting in the git plugin which will prefix every command line git call with `setsid` (on platforms where a setsid program is available). However, it is a system property and not readily available to typical users.

dnusbaumsorry missed this. I used ssh with private key when I did my test. That is interesting about the setsid but I was not actually doing this checkout on an agent and was instead doing it on the master.

Did you guys run it on the master as well?

ataylor the crucial attribute is whether the process that invokes command line git (agent or master) has a controlling terminal attached. If you ran "jenkins.war" from the command line, then you were running in the foreground unless you took special steps like:

• prefix command with `setsid`
• redirect stdin from /dev/null (maybe, never tried this one, but think it should work)
• run in the background and redirect stdin from /dev/null (maybe, never tried this one, but think it should work)

I have not checked the behavior of a master running on Windows, just agents on Windows.

ataylor On my macOS master, it doesn't work for the reasons that Mark explained (the terminal is interactive, so it prompts for the key at the command line, which doesn't work). Once I used setsid and a local JNLP agent it worked fine.

Are you getting a timeout, or a public key error?

markewaite Yeah I think the setsid is probably affecting me because I am running Jenkins from the terminal.

But my question would be how do I go about adding setsid on a master? I could normally add it onto the prefix to the agent but if I am doing a checkout on master then how would I add it?

If the master is running as a service (for example, as installed by the rpm file on CentOS, the deb file on Debian, the pkg file on FreeBSD), then setsid is not needed. Services are already running without a controlling terminal.

If the master is running in the foreground and your computer has a command `setsid` in the PATH, then you could pass the java property:

org.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true

ataylor There is no setsid shell command on macOS, so you have to compile https://github.com/jerrykuch/ersatz-setsid locally (make setsid), but once you do that I would expect that you could just run `/path/to/setsid java -jar jenkins.war` and then run a build on on the master.

ataylor the conversation seems to indicate that the problem you're detecting is related to executing Jenkins in the foreground on a machine that does not have the setsid command (not available on macOS or FreeBSD). I've marked this as resolved as a duplicate of JENKINS-20879.

If I've misunderstood, please reopen the bug with more description of the failure mode.