Git

FYI - 

For others who were having this issue, I was able to get a repo to work with GitHub.

Name/Desc field: whatever you want
Repository Location: git@github.com:<proj>/location-to.git
(This can be seen when logged into github and looking at your repo... 
Click on SSH rather than HTTP for the location)
Path: BlankBlock Size: Blank
Rename Detection: Copy

You will also need to setup ssh keys on the crucible/fisheye server (see here: http://help.github.com/msysgit-key-setup/)
Then also, you will need to have it stop prompting for a password (see here: http://help.github.com/working-with-key-passphrases/)

Also you will need to setup .gitconfig under the home dir of the user you are running crucible/fisheye as:

[root@crucible ~]# cat .gitconfig
[user]
name = githubuser1234
email = githubuser1234@somecompany.com

Using my best guesses I get:

Error
Error calling server:com.atlassian.fecru.gwt.admin.shared.OperationFailureException: Failed to enable or start new repository authorised-cas-proxy Unknown.fGb(Unknown source:0) Unknown.lGb(Unknown source:0) Unknown.lPc(Unknown source:0) Unknown.ks(Unknown source:0) Unknown.WMc(Unknown source:0) Unknown.QNc(Unknown source:0) Unknown.Cbc(Unknown source:0) Unknown.ecc(Unknown source:0) Unknown.anonymous(Unknown source:0) Unknown.n2b(Unknown source:0) Unknown.anonymous(Unknown source:0) Unknown.anonymous(Unknown source:0)
You are running release CR2.4.1 FE2.4.1 (20101027024419 2010-10-27), please report your release number when reporting bugs.
Got a suggestion or an issue?
Discuss it in our forums or visit our support website for other options.

It would be helpful to demonstrate the full set of configuration cases and in particular the setup of a repo for access using ssh keys, since that is the most common git usage pattern out there. Unfortunately, this appears to be another case of insufficient usage documentation.

We found documentation greatly lacking for SSH connectivity, below shows how we finally successfully implemented.

On Linux, we recently and finally successfully connected Fisheye using SSH as user 'git' to a github repository to access a particular git repo.

Fisheye Repo Definition:
Repository Location: ssh://git@github.xx.yyy/GEMINI/GEMINI.git
Git Authentication: Generate key pair for ssh
This created a private key file at /FISHEYE_INST/data/auth/GEMINI-xxx and public key file at /FISHEYE_INST/data/auth/GEMINI-xxx.pub the later was sent to Github owner to install on their end.

Found for /home/username-fisheye-runs-as/.ssh we had to create a file named config with contents like: (So ssh would logon to github as user 'git'.)
Host github.xx.yyy
User git

Also had to copy the private and pub keys to /home/username-fisheye-runs-as/.ssh dir.

Connection then was successful and we have been polling github repo successfully since.

Other Notes:
Misleading Error Message - (prior to configuring .ssh/config file)
Prior to configuring .ssh files, we were getting a Fisheye message (after Test Connection):
Fisheye is using '/usr/bin/ssh' to authenticate with
SSH authenticated repositories. Error testing
connection. Error talking to repository:
ssh: git-upload-pack: Name or service not known
fatal: The remote end hung up unexpectedly

Research on web led to multiple hits with various solutions that were of NO VALUE and confusing, because in fact, we were connecting as 'username-fisheye-runs-as' and the git repo we were connecting to only allows user 'git'. So we really were not even making a successful ssh connection.

After installing Git client found Fisheye was looking in /home/username-fisheye-runs-as/share/git-core for 'templates' so we updated directory structure to match what Fisheye seemed to need.

-craig

Is there an equivalent to the Subversion option for Start Revision? I am limited to only 10 committers, so I only want to index a subset of the revisions.