This documentation relates to an earlier version of FishEye.
View

Unknown macro: {spacejump}

or visit the current documentation home.

When adding or managing a SVN (Subversion) repository, you can:

There are also the following SVN-specific actions:

It is particularly important that you set up the correct branch and tag structure for your Subversion repositories. If FishEye does not know which files are tags and branches, it will treat all files as trunk files. This can significantly increase the effective size of your repository. This will increase initial scan time and impact runtime performance. Please refer to the instructions on tag and branch configuration.
In the majority of cases, indexing a small repository shouldn't take hours, and certainly not days. However, if you have a giant repository, have a slow remote host, you're using HTTP or HTTPS protocols, or if there is a problem with the symbolic setup of your repository, it could potentially take hours or even days. If in doubt, schedule the indexing to run over a weekend or extended maintenance period.

Using the 'file://' protocol to access your Subversion repository can be much faster than the other network protocols. We recommend using the 'file://' protocol if possible.

ナレッジベース

You may find some useful information in the Knowledge Base too.

SVN Repository Details

詳細

説明

名前

A name for this repository. The name may contain alphanumeric, underscore, '-' or '.' characters. Use 'svn' if you can't think of a better name.

説明

A short description of this repository.

リポジトリ タイプ

The type of repository - select "Subversion"

Store Diff Info

Enable this option if you are using the Subversion or Perforce SCM systems and making use of per-author line counts. Otherwise, enabling this option is not necessary. Read more information

SVN URL

The Subversion Repository Root URL to your repository, such as svn://svn.foo.com or file:///var/svn. If you are not sure what your repository root is, check the section below "Finding your Repository Root".
(Please note that file protocol performs the fastest followed by svn and lastly by http/s. Therefore where possible please use the file protocol.)

パス

The sub-tree within your repository that FishEye should display. If this value is '.' (or empty), then the whole repository will be shown.

Block Size

Controls how many revisions FishEye will pull down from the repository in one batch. Larger values can reduce the time it takes for FishEye to scan your repository for changes, but use more memory. Smaller values can reduce the amount of memory FishEye uses during scans. The default is 400.

Svn Operation Timeout

Sets the timeout value that FishEye imposes on Subversion operations. Operations which exceed this value are terminated. The default for most operations is 1 hour. It can be changed to a different interval, for example: "2 days", "10 hours", or "20 minutes".

Throttle connections-per-sec

If set, this allows FishEye to throttle how many connections it makes per second to the SVN server. Many systems use inetd/xinetd to service the svnserve protocol. xinetd has, by default, an incoming connection limit which can cause FishEye to disrupt other svnserve-based connections. The default is blank (do not throttle).

文字セット

The character set used to interpret and display text files.

Access Code

The access code for the fisheye.access property on the server. See also Subversion fisheye.access.

MD5 Access Code

The MD5 sum of the above Access Code. See also Subversion fisheye.access. (This field only appears if Access Code is set.)

Set Access Property Command

The Subversion command to set the fisheye.access property to grant FishEye access if necessary. See also Subversion fisheye.access. (This field only appears if Access Code is set.)

Start Revision

If set, the revision number from which FishEye will start indexing the repository. The default is to start scanning from the first revision in the repository.

Initial Import

When a Start Revision is set, this setting controls how FishEye establishes the initial state of the repository.
'Do not import' means that FishEye will only process the revisions from the start revision onwards. The repository state prior to this revision is ignored.
'Import without tag information' means that FishEye will import the repository content as it existed one revision prior to the start revision. FishEye will create a single synthetic revision to hold the initial state. The comment associated with this revision will be 'Created by FishEye for initial repository import'. Tags created prior to the start revision are ignored.

Username/Password

The credentials to use if your repository requires authentication.

Follow Base Moves

If you have changed the location of your repository in your Subversion server over time, set this option to true. Doing so will cause FishEye to index your repository's full history across all its locations within your server.

trunk/branch/tag structure

Determines how FishEye attempts to understand the tag and branch structure of your Subversion repository. Read more information.

Enable immediately

Controls whether FishEye will immediately enable this repository, which starts the initial scan. If you wish to do some further configuration before the scan starts, then select 'No'. You can enable a repository later from the repository list.

If FishEye returns the error 'Authentication Cancelled', this may simply indicate an incorrect username or password.

Finding your Repository Root.

次のコマンドを実行します。

svn info SVN_URL

Where SVN_URL is the complete URL of the repository you want to add.

You will get something like the following:

>svn info http://svn.example.com/svn5/

Path: svn5
URL: http://svn.example.com/svn5/
Repository Root: http://svn.example.com/
Repository UUID: ce062a09-193b-427a-a7b3-a85007076e5d
Revision: 83
Node Kind: directory
Last Changed Author: ryan
Last Changed Rev: 83
Last Changed Date: 2009-05-07 10:48:41 +1000 (Thu, 07 May 2009)

Next to "Repository Root" is the URL you should define as your repository root. The path will be whatever is remaining.

Screenshot: Adding a SVN Repository


9 Comments

  1. Anonymous

    Apr 11, 2010

    How should the info be entered when having several repositories served from one root url?

    We have a layout like this:

    svn.domain.com/repo1

    svn.domain.com/repo2

    If I enter file://source for the url it will fail.

    If I enter file://source for the url and repo1 for path it will index, but show nothing.

    If I enter file://source/repo1 for the url and nothing in path it works correctly, but will mean that I have to configure each child repository.

  2. Ron Summers

    Aug 10, 2010

    How about filling in the SVN URL and Path boxes in the screenshot so it is more obvious how those should be filled out.  For instance, does the end of the SVN URL need to end in a slash?  Does the path need to start with a slash?

  3. Anonymous

    Dec 13, 2010

    I agree, I'm struggling to set up our SVN repo, and it shouldn't be this hard.

  4. Anonymous

    Jan 04, 2011

    My subversion repository is accessible via svn+ssh by ssh public key authentication. How can I configure or add an ssl key pair to crucible?

    1. Anonymous

      Jul 08, 2011

      I'm waiting for a response on this too.

      1. Jaroslav Pantsjoha

        Feb 27, 2012

        Im awaiting any sort of response regarding this as well.

         

        tried playing with stunnel and config for .ssh... not doing so well.

    2. Anonymous

      Jul 19, 2012

      I haven't tried that variant myself yet, but does creating a ssh-key for the user which is running the process work?

      assuming that you "su - fisheye" before you start the bin/start.sh, you might just need to do a "ssh-keygen -b 2048" (confirm default locations) to generate a key. the .ssh/id_rsa.pub file will contain your public key then (which you have to add on the server obviously).

      maybe you will have to manually connect once per ssh to add the SVN servers host key to your known_hosts.

       

  5. billbuie

    Jan 18, 2011

    I would think that if FishEye can communicate with the Subversion instance through an URL, then a FishEye instance hosted by Atlassian should be able to shadow a Subversion instance hosted locally.  The initial scan might take a while, but once it's up, I'd expect it should work fine.

    However, someone has told me that they'd heard that if Atlassian hosts FishEye, then Atlassian must host Subversion as well.

    Can anybody defnitively say that they know of someone who is using the Atlassian-hosted FishEye while they host their own repositories?

  6. Anonymous

    Feb 17, 2012

    How about adding that UserName/Password gets grey'd out, but having a selection to use the LDAP authentication settings used by the person whom just logged into fisheye/jira.



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.