Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327274 - svn does not support http://
Summary: svn does not support http://
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-07 16:01 EDT by Jesse McConnell CLA
Modified: 2010-10-12 16:26 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse McConnell CLA 2010-10-07 16:01:47 EDT
https://hudson.eclipse.org/hudson/job/jetty/708/console

[ERROR] svn: Unrecognized URL scheme for 'http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk'


I use the maven-scm-plugin to export a checkout of the jetty tag/trunk when building the distributions so as to also contain a -src archive.  That is not working on hudson.eclipse.org at the moment.  Is this on purpose or an oversight on svn configuration?

cheers,
jesse
Comment 1 Denis Roy CLA 2010-10-07 16:21:25 EDT
Jesse, I'd ask on the cross-project mailing list.  Many are using Maven, many of which likely use svn.
Comment 2 Jesse McConnell CLA 2010-10-07 16:35:21 EDT
What am I to ask?  It is not an issue with maven but with the svn executable on hudson.eclipse.org not being configured to support http://

Below is the specific command being executed on the build machine and pasted in the description is the error output from the svn command.

[INFO] Executing: /bin/sh -c cd /opt/users/hudsonbuild/workspace/jetty/jettytrunk/jetty-distribution/target/export && svn --non-interactive export --force http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk /opt/users/hudsonbuild/workspace/jetty/jettytrunk/jetty-distribution/target/export

My question on if this was intentional was based around if not having http support in the svn command was a choice or just an oversight.

cheers
Comment 3 Denis Roy CLA 2010-10-07 16:40:11 EDT
Oh, the svn _client_ on Hudson doesn't support http.  I understand.  I thought you were talking about our svn servers, which do support SVN.

This was not intentional -- the svn package we use is compiled in-house, and I wasn't aware we had to turn anything 'on'.  I'll look into it, but in the meanwhile, can you use svn:// instead of http:// ?
Comment 4 Jesse McConnell CLA 2010-10-07 16:43:41 EDT
Not without changing scm urls that I am not keen on tweaking, what I can do is just disable that part of the build for the time being, maybe look at re-enabling it next week?  Not sure what your timeline is on 'looking into it'.  Also given how much longer this build is taking compared to what it used to I am considering shoving some of these sorts of things over to just the release builds so it might be a 'critical' thing for me to have.

anyway, thanks!
Comment 5 Eclipse Webmaster CLA 2010-10-12 16:26:07 EDT
I've rebuilt SVN on hudson and it seems to be happy with http. 

-M.