Ioannis Mavroukakis

To be more precise `clean test release -Prelease.disableChecks -Prelease.pushTagsOnly -Prelease.customKeyFile="/home/jenkins/.ssh/id_rsa"`

No and that's the point I'm making. 22 isn't open, hence we use `corkscrew` to tunnel ssh traffic through our web proxy. Normally, this is something that's transparent to git...

It's actually quite common to use corkscrew or some other proxy, to route `[email protected]` requests to `ssh.github.com:443` via a proxy..think this can be done as things stand?

Thanks again. GitHub themselves have setup `ssh.github.com:443` just because some corporate firewalls can be overly restrictive..

Some interesting reading https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-WhyNotJGit So in essence, you can use https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin and have it as a configurable option whether the local git instance will be used or JGit

In a nutshell yes. But the main issue seems to be that JGit simply doesn't provide parity with the git CLI. What git-client provides is essentially a bridge between the...

oh and a very Happy New Year :smiley_cat:

We'll see what we can do :)

There's a lot of us still on the 2.x branch and won't just jump to 3.x when it comes out, your plugin is still mega-useful :+1: