|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-14131) scm-sync-configuration doesn't work with git/ssh if the server key wasn't accepted
bertrand.paq...@gmail.com (JIRA) Mon, 25 Jun 2012 13:43:39 -0700
- [JIRA] (JENKINS-14131) scm-sync-configura... aherit...@apache.org (JIRA)
- [JIRA] (JENKINS-14131) scm-sync-conf... fcamb...@java.net (JIRA)
- [JIRA] (JENKINS-14131) scm-sync-conf... fcamb...@java.net (JIRA)
- [JIRA] (JENKINS-14131) scm-sync-conf... bertrand.paq...@gmail.com (JIRA)
- [JIRA] (JENKINS-14131) scm-sync-conf... fcamb...@java.net (JIRA)
- [JIRA] (JENKINS-14131) scm-sync-conf... bertrand.paq...@gmail.com (JIRA)
- [JIRA] (JENKINS-14131) scm-sync-conf... bertrand.paq...@gmail.com (JIRA)
Fred, it's not a credential problem. The problem is to clone a repo when the SSH server key has never been accepted.
I have tested with the Git Jenkins plugin : with java -jar jenkins.jar, the plugins ask in the console for accept server key ...
The problem is not handled by git plugin, I think update the documentation is only thing we can do.