Analyzing Subversion connectivity issues with JSVN
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
Fisheye/Crucible ships with JSVN - a SVNKit java command-line client. The JSVN command-line client effectively functions like the Subversion Command-Line Client except that it works with the Java libraries in Fisheye/Crucible.
To run the SVNKit Java command-line client:
Linux/Unix:
Navigate to the Fisheye/Crucible installation directory:
<FishEye installation directory>/lib/svn
Update the permissions on the JSVN script by running the following command:
chmod 777 jsvn
Run the
jsvn
script../jsvn --help
can be used for a list of available commands.
Windows:
Navigate to the Fisheye/Crucible installation directory:
<FishEye installation directory>
/lib/svn
Run the
jsvn.bat
script.
Usage example (diff between revisions 2500 and 2501 for username USER and password PASS):
1
jsvn --no-auth-cache --username USER --password PASS diff -r 2500:2501 https://svn.repo.com/REP/@2501
For instructions on how to use the Subversion command-line client, please refer to the
Subversion Command Line Client 1.5
documentation.
Was this helpful?