Work out how to test SVN Components when SVN goes away

Description

We discussed this and it fell off my list. Putting it here so I don't forget again.

We support Resource access to SVN and it is widely used (I think). We test this (a bit) via access to our own SVN repo.

Our SVN repo is about to go away and so we need a better way of testing.

Options which srping to mind are

  • "Borrow" someone else's SVN (like Apache). Very sucky for automated tests, but a definite possibiloty for tests which are left there to help us in the face of regressions

  • float an internal only SVN repo. I cannot find a Java SVN repo

  • Use file: URI's for svn. Needs investigation

Environment

None

Activity

Rod Widdowson 
March 20, 2017 at 2:10 PM

Fixed by 5f659c0

This checks a small SVN repo into the resources and checks it out. Needed the use of .gitattributes to set the repo to not be text

Rod Widdowson 
March 19, 2017 at 3:11 PM

My brain leaks at the idea of having an svn repository checked into a git one. but it looks as though it will work.

Fixed

Details

Assignee

Reporter

Fix versions

Affects versions

Created January 23, 2017 at 11:01 AM
Updated October 9, 2018 at 5:59 PM
Resolved March 20, 2017 at 2:10 PM