Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-622

Need doco for how to connect to subversion repository using the svn+ssh protocol.

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently it is possible to connect to a svn repository using the svn+ssh:// protocol.

      We need doco for this.

      +++++++++++++
      You first need to confirm what type of authentication method (username/password or private key) is used by the "svn+ssh" server.
      If it uses username and password then you set it up as normal.
      If the SVN server uses private key as its authentication method and your Fisheye instance uses SVNKit to connect to SVN repository, you may want to follow through the following documentation in order to enable the svn+ssh to authenticate with private key:

      Essentially, svnkit.ssh2.key properties is only needed when the ssh key is already uploaded to server for authentication (no username and password given).

      In that case, you need to use the following system properties to let SVNKit know about your private key and passphrase:

      svnkit.ssh2.key = /path/to/private/key/file 
      svnkit.ssh2.username = userName  
      svnkit.ssh2.passphrase = optionalPassphrase 
      svnkit.ssh2.password = userpassword
      svnkit.ssh2.port = optionalPort
      

      You can do that by setting FISHEYE_OPTS environment variable:

      export FISHEYE_OPTS="-Dsvnkit.ssh2.key=/path/to/private/key/file -Dsvnkit.ssh2.username=userName -Dsvnkit.ssh2.passphrase=optionalPassphrase -Dsvnkit.ssh2.password=userpassword -Dsvnkit.ssh2.port=optionalPort"
      

      +++++++++++++

      Need to check with someone from development if this is all that is needed. I got the following info from past support cases

            [FE-622] Need doco for how to connect to subversion repository using the svn+ssh protocol.

            Atlassian Update – 31 January 2020

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 31 January 2020 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Kind regards Marek Parfianowicz Development Team Lead

            MattS added a comment -

            If the ssh key has been uploaded to the svn server, does that mean that the userpassword is optional? There is a KB article about this topic at https://confluence.atlassian.com/display/FISHKB/Cannot+Access+SVN+Repository+Over+SSH+Due+to+Error+-+svn+authentication+cancelled

            MattS added a comment - If the ssh key has been uploaded to the svn server, does that mean that the userpassword is optional? There is a KB article about this topic at https://confluence.atlassian.com/display/FISHKB/Cannot+Access+SVN+Repository+Over+SSH+Due+to+Error+-+svn+authentication+cancelled

            Never mind, got it working. Thanks for posting this. Documentation was hard to find, and its a feature that lots of people would use.

            Philip Crockett added a comment - Never mind, got it working. Thanks for posting this. Documentation was hard to find, and its a feature that lots of people would use.

            I tried setting the FISHEYE_OPTS variable in Windows and it still didn't work.

            Philip Crockett added a comment - I tried setting the FISHEYE_OPTS variable in Windows and it still didn't work.

              pwatson paulwatson (Inactive)
              pkamal Partha
              Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: