Analyzing Subversion connectivity issues with JSVN

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server only. This article only applies to Atlassian products on the Server platform.

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:
    1. Navigate to the Fisheye/Crucible installation directory: <FishEye installation directory>/lib/svn
    2. Update the permissions on the JSVN script by running the following command: chmod 777 jsvn
    3. Run the jsvn script. ./jsvn --help can be used for a list of available commands.
  • Windows:
    1. Navigate to the Fisheye/Crucible installation directory: <FishEye installation directory>/lib/svn 
    2. Run the jsvn.bat  script.
Usage example (diff between revisions 2500 and 2501 for username USER and password PASS):


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.
Last modified on Jan 24, 2025

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.