[JIRA] (JENKINS-8871) Allow to use other SVN protocol than http/https
[ https://issues.jenkins-ci.org/browse/JENKINS-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160488#comment-160488 ] Jose Pedro Correia commented on JENKINS-8871: - 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... Allow to use other SVN protocol than http/https --- Key: JENKINS-8871 URL: https://issues.jenkins-ci.org/browse/JENKINS-8871 Project: Jenkins Issue Type: Improvement Components: scm-sync-configuration Reporter: fcamblor Assignee: fcamblor Attachments: scm-sync-configuration-0.0.5-bugfix8871-1.hpi 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8871) Allow to use other SVN protocol than http/https
[
https://issues.jenkins-ci.org/browse/JENKINS-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159751#comment-159751
]
Pedro Correia commented on JENKINS-8871:
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]:
{code}
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 ..
{code}
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:
{code}
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'
{code}
This is strange because I'm pretty sure the credentials are set up correctly...
Any thoughts?
Allow to use other SVN protocol than http/https
---
Key: JENKINS-8871
URL: https://issues.jenkins-ci.org/browse/JENKINS-8871
Project: Jenkins
Issue Type: Improvement
Components: scm-sync-configuration
Reporter: fcamblor
Assignee: fcamblor
Attachments: scm-sync-configuration-0.0.5-bugfix8871-1.hpi
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8871) Allow to use other SVN protocol than http/https
[ https://issues.jenkins-ci.org/browse/JENKINS-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159770#comment-159770 ] fcamblor commented on JENKINS-8871: --- Hi Pedro, I just created https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings Can you please see if it can help ? Allow to use other SVN protocol than http/https --- Key: JENKINS-8871 URL: https://issues.jenkins-ci.org/browse/JENKINS-8871 Project: Jenkins Issue Type: Improvement Components: scm-sync-configuration Reporter: fcamblor Assignee: fcamblor Attachments: scm-sync-configuration-0.0.5-bugfix8871-1.hpi 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
