This post will spare you some pain authenticating with Jenkins running on a Windows machine. In particular this post is about the obstacles to getting Jenkins and Bitbucket communicating (link).
If you try to authenticate with HTTPS you get "jenkins returned status code 255: stdout: stderr: error: could not lock config file .git/config: No such file or directory". The bug report (link) comments indicate that the problem is purely cosmetic, or caused by upgrade issues (link). However, I couldn't get my Bitbucket / Jenkins integration working until I resolved this despite it being a fresh (unupgraded) install. Fortunately a Stack Overflow question (link) suggested just avoiding HTTPS authentication entirely and using SSH as a work-around.
I tried verifying that Bitbucket was trying to connect to Jenkins by enabling an access log for Jenkins, but that feature seems to be Linux only (Google search).
If you try authenticating with SSH by reading the docs (link) then you can get a "git plugin only support official git client" error. I found that this bug should be fixed (link), but with GIT plugin 2.0.1 (link) and GIT client plugin 1.6.1 (link) I still had the problem. You can verify by looking at the source (link, line 1041).
I tried setting the GIT_SSH environment variable (link) and ensuring that Git/bin was on my path to no avail. In contrast I had some success trying polling in the short term instead of having Bitbucket notify my Jenkins server when there was a code check-in (link).
The final solution (besides re-installing in the default location) was to use Junction Link Magic (link) to create a hard link (aka a junction in windows terminology) from the default location to the actual location.
In summary the only way to get Jenkins working correctly on Windows is to use SSH instead of the default HTTPS and with an alternate Git install location you have to create a hard link (junction) from "C:/Program Files (x86)/Git" to where you installed Git.
No comments:
Post a Comment