Repository Scan Fails due to Incorrect SVN Path
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
A warning message similar to the following is printed in the logs when trying to scan your Subversion repository:
1
2
3
2010-01-01 10:10:10,100 WARN [InitialPinger1] fisheye.app SvnRepositoryTester-checkRepoSettings -
Repository URL svn+ssh://user@svn.example.com does not match URL returned from repository: svn+ssh://user@svn.example.com/svn/myproject
Cause
This is caused due to incorrect SVN URL / SVN Path mapping in Fisheye. The following setting is incorrect:
SVN URL | svn+ssh://user@svn.example.com |
|---|---|
SVN Path | /svn/myproject |
Resolution
In the above example, Subversion repository root is actually svn+ssh://user@svn.example.com/svn/myproject. The settings should therefore be:
SVN URL | svn+ssh://user@svn.example.com/svn/myproject |
|---|---|
SVN Path | (empty) |
Was this helpful?