-
Suggestion
-
Resolution: Unresolved
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
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[FE-622] Need doco for how to connect to subversion repository using the svn+ssh protocol.
| Fix Version/s | New: N/A [ 54414 ] |
| Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
| Labels | Original: FE_CRU_SUPPORT documentation | New: FE_CRU_SUPPORT documentation jac-cleanup-phase7 |
| Workflow | Original: JAC Suggestion Workflow [ 3338637 ] | New: JAC Suggestion Workflow 3 [ 3642932 ] |
| Backlog Order (Obsolete) | Original: 980000000 | |
| Workflow | Original: Simple Restricted [ 2952058 ] | New: JAC Suggestion Workflow [ 3338637 ] |
| Issue Type | Original: Task [ 3 ] | New: Suggestion [ 10000 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: FECRU Development Workflow - Triage - Restricted [ 1518399 ] | New: Simple Restricted [ 2952058 ] |
| Labels | Original: FE_CRU_SUPPORT | New: FE_CRU_SUPPORT documentation |
| Workflow | Original: FECRU Development Workflow - Triage [ 944758 ] | New: FECRU Development Workflow - Triage - Restricted [ 1518399 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 163814 ] |
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