Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: scm-sync-configuration-plugin
-
Labels:None
Description
Prior to v0.0.3, scm-sync-configuration plugin is relying on svnjava maven scm provider (see http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/ ), only http/https/file protocols are supported (for example svn+ssh is not supported).
Eventually, a workaround would be to activate svnexe maven scm implementation for these case (Problem is : I don't know if we can have both svnexe & svnjava plexus component activated in the same time)
Nevertheless, the best point would be to have svnjava be compliant with every svn supported protocols.
Issue Links
- depends on
-
JENKINS-18129
Using credentials-plugin to authenticate against SCMs & getting rid of maven-scm-api
-
- Open
-
- is duplicated by
-
JENKINS-14948
Cannot commit the configuration change
-
- Closed
-
- is related to
-
JENKINS-338
Cannot use svn protocol for Subversion
-
- Closed
-
-
JENKINS-14792
Can't authenticate with HTTPS client cert + username/password
-
- Reopened
-
Activity
Hi everyone,
Don't know if anybody is still busy with this, but I was trying to get this working.
Initially I ran into the same problem as reported by jchatham:
Mar 2, 2012 1:41:15 PM hudson.plugins.scm_sync_configuration.SCMManipulator checkout SEVERE: [checkout] Error during checkout : SVN checkout failed. Mar 2, 2012 1:41:15 PM hudson.plugins.scm_sync_configuration.SCMManipulator scmConfigurationSettledUp INFO: Creating scmRepository connection data ..
To try to fix this I manually checked out the JENKINS_HOME/scm-sync-configuration/checkoutConfiguration directory. That solves that problem, but now I get problems committing changes to the configuration files:
Mar 2, 2012 1:48:13 PM hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles SEVERE: [checkinFiles] Problem during commit of [[config.xml]] : svn: Commit failed (details follow): svn: Authentication required for 'svn+ssh://tk7'
This is strange because I'm pretty sure the credentials are set up correctly...
Any thoughts?
Hi Pedro,
I just created https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings
Can you please see if it can help ?
Hi fcamblor,
Thanks for the feedback (I just saw it now, sorry).
I tried out that test job. It worked fine. However, I still have exactly the same problem...
The very standard Subversion svn:// protocol is supported since release 1.514 , release May 1st, 2013.
Problem got fixed in 1.514 by upgrading internal plugins.
After some debugging, it looks like the bug is at ScmSyncSubversionSCM.java:58, where the kind variable is set to the empty string. Each implementation of the abstract Credential.createSVNAuthentication() method checks the value of this parameter to make sure it matches the type of authentication each subclass can create, so passing an empty string always fails. I hard-coded kind to ISVNAuthenticationManager.SSH, and I was able to get a little further.