-
Improvement
-
Resolution: Fixed
-
Major
-
None
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.
- depends on
-
JENKINS-18129 Using credentials-plugin to authenticate against SCMs & getting rid of maven-scm-api
- Closed
- 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
- Closed