Jenkins pipeline and ssh creds

[Kurt T Stam]

Hey guys,

I'm running a jenkins pipeline with a private git repo. I found that ssh
keys on the master only work when use the git binary, rather then jgit
which is a jenkins global config setting. How do I make a permanent
jenkins config change? Or does anyone know of a better workaround.

Thx,

--Kurt

[James Rawlings]

Hey Kurt, what's the config change that you need to make?

> --
> You received this message because you are subscribed to the Google Groups "fabric8" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[James Strachan]

can't we point jgit at the same ssh keys somehow? Not sure where jgit looks for the keys mind you ;)

--
You received this message because you are subscribed to the Google Groups "fabric8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

James
-------
Red Hat

Twitter: @jstrachan
Email: james.s...@gmail.com

Blog: https://medium.com/@jstrachan/

fabric8: http://fabric8.io/

open source microservices platform

[Ioannis Canellos]

I would assume that you would have to go via the credentials plugin.

--

Ioannis Canellos

Blog: http://iocanel.blogspot.com

Twitter: iocanel

[Kurt T Stam]

Under 'Manage Jenkins > Configure System', I add 'Git' and pointed it to the binary, and I moved it first in the list.

[Kurt T Stam]

Y .. all I can find thus far is that jgit allows you to set the keys per job. Which is good for a cloud deployment, just haven't figured out how this works exactly.

[Kurt T Stam]

Well actually I did figure that out, you're required to point it to a specific credential in the job definition, so you can't leave it 'none' anymore, and assume it will pick up you keys in your .ssh directory. This is why I asked James R before how to script a global credentials and how to script using it for the job definition.

[James Rawlings]

using the global credentials is a PITA as the id's change so can't really be referenced inside the Jenkinsfile, ideally we should be able to use one way to manage credentials on kubernetes and openshift and that being secrets.

If it works after adding the Git configuration you could just find what that looks like in the Jenkins config.xml of the Jenkins master, then add it into the jenkins image, my guess it'll be added in here https://github.com/fabric8io/jenkins-docker/blob/master/config/config.xml

then 

docker build -t fabric8/jenkins-docker:test .

edit your Jenkins RC image name to point to the image above and see if that works?

[Jimmi Dyson]

I wonder if it would be possible to have a Kubernetes Secret type of Jenkins credential provided in the Kubernetes plugin (or elsewhere)?

[Kurt T Stam]

On 7/8/16 3:50 PM, James Rawlings wrote:

using the global credentials is a PITA as the id's change so can't really be referenced inside the Jenkinsfile, ideally we should be able to use one way to manage credentials on kubernetes and openshift and that being secrets.

I may not fully grasp what runs where, but the issue is on the master, not the builder. The creds are ok in the builder. The fact that the jenkins file is mentioned in the job's configuration makes me think that it is configured outside of the Jenkinsfile.

If it works after adding the Git configuration you could just find what that looks like in the Jenkins config.xml of the Jenkins master, then add it into the jenkins image, my guess it'll be added in here https://github.com/fabric8io/jenkins-docker/blob/master/config/config.xm

then 

docker build -t fabric8/jenkins-docker:test .

edit your Jenkins RC image name to point to the image above and see if that works?

OK will give that a shot.

[Kurt T Stam]

Hi James,

https://github.com/fabric8io/jenkins-docker/blob/master/config/hudson.plugins.git.GitTool.xml

points to jgit.

On 7/8/16 3:50 PM, James Rawlings wrote: