Jenkins build depends on java.net svn infra

[Olivier Lamy]

Hi Folks,

Our build depends on java.net svn infra for some unit tests (see [1]).

So two solutions :
* copy this https://svn.java.net/svn/hudson~svn/trunk/hudson/test-projects
in a new code.google.com project
* setup a new repo in https://github.com/jenkinsci/test-projects with
the content from java.net (and use svn mode capability from github [2]
in unit test )

WDYT ?

Thanks,
--
Olivier Lamy
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7

[1] https://github.com/jenkinsci/jenkins/blob/master/test/src/test/java/hudson/maven/MavenBuildTest.java
[2] https://github.com/blog/626-announcing-svn-support

[Jerome Lacoste]

On Thursday, February 3, 2011 10:12:58 AM UTC+1, Olivier Lamy wrote:

Hi Folks,

Our build depends on java.net svn infra for some unit tests (see [1]).

So two solutions :
* copy this https://svn.java.net/svn/hudson~svn/trunk/hudson/test-projects
in a new code.google.com project
* setup a new repo in https://github.com/jenkinsci/test-projects  with
the content from java.net (and use svn mode capability from github [2]
in unit test )

WDYT ?

Or rewrite the tests. Don't see why they involve SVN at all. They are MavenBuild tests.

Why aren't we using  an extractResource SCM there ? Or some mocking if the goal was to trigger a particular failure.

Jerome

[Jerome Lacoste]

Taking...

[Wei-ju Wu]

I see why they some tests would depend on a version control system,
but agree mocking the SCM would be a good idea.

Wei-ju

[Andrew Bayer]

I'm willing to bet the test predates ExtractResourceSCM - I don't see a good reason *not* to rewrite the tests to use ExtractResourceSCM instead.

A.