[JIRA] (JENKINS-14131) scm-sync-configuration doesn't work with git/ssh if the server key wasn't accepted

[fcamb...@java.net (JIRA)]

Frédéric Camblor commented on JENKINS-14131 scm-sync-configuration doesn't work with git/ssh if the server key wasn't accepted To my POV, the maven scm api is not the best way to implement this because : Generally, it relies on filesystem properties (like ~/.svn) which make things hard to reproduce / upgrade from jenkins and You won't benefit from jenkins stored credentials That's why the hudson.plugins.scm_sync_configuration.scms.SCM is made for : provide an abstraction above hudson.scm.SCM to retrieve credentials using jenkins stored credentials (see https://github.com/jenkinsci/scm-sync-configuration-plugin/blob/master/src/main/java/hudson/plugins/scm_sync_configuration/scms/ScmSyncSubversionSCM.java) Note that for everything else (for the moment, it can change in the future), I rely on maven scm api for standardization about commit, updates, etc... What is lacking in the Git implementation, is the implementation for the extractScmCredentials(). I must admit I had a hard part making it work (and even... "work" is a big word here...) for the SVN implementation. But yours is totally empty. That's why if repository is never initialized first, it will never work.

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