- In windows, Jenkins will use the the SSH key of the user it is running as, which is located in the %USERPROFILE%\.ssh folder ( on XP, that would be C:\Documents and Settings\USERNAME\.ssh, and on 7 it would be C:\Users\USERNAME\.ssh). Therefore, you need to force Jenkins to run as the user that has the SSH key configured. To do that, right click on My Computer, and hit "Manage". Click on "Services". Go to Jenkins, right click, and select "Properties". Under the "Log On" tab, choose the user Jenkins will run as, and put in the username and password (it requires one). Then restart the Jenkins service by right clicking on Jenkins (in the services window), and hit "Restart".
- Jenkins does not support passphrases for SSH keys. Therefore, if you set one while running the initial Github configuration, rerun it and don't set one.
9 (Jul 1, 2014)
- Webhook auto management now works with GitHub Enterprise (JENKINS-18710)
- GitHub Web Hook does not work unless "Prevent Cross Site Request Forgery exploits" is disabled (JENKINS-20140)
- Fixed NPE trying to save a job (JENKINS-20201)
Version 1.7 (Jul 7, 2013)
- Add the name of the user who pushed to Github into the log (pull #17).
- Recognize GitHub repository URLs that doesn't end with ".git"
- Got rid of API token and added OAuth token for interacting with GitHub.
- Webhook support is no longer a pre-requisite for commit status notification (JENKINS-18165)