Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-7923

If GIT_SSH_COMMAND is set, FishEye SSH does not execute to index Bitbucket Server Repo

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • N/A
    • None
    • 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.

      Problem Definition

      FishEye fails to index Bitbucket Server repositories if the environment variable GIT_SSH_COMMAND is set:

      2016-12-03 18:44:25,348 WARN  [IncrPing2 repo ] fisheye IndexingPingRequest-doRequest - Exception during FishEye Incremental Indexing of repo (repo): com.cenqua.fisheye.config.ConfigException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: Permission denied (publickey).
          fatal: Could not read from remote repository.
          
          Please make sure you have the correct access rights
          and the repository exists. 
      

      With the GIT_SSH_COMMAND variable being set, the fe-ssh.sh script is never executed meaning FishEye never makes the SSH call to Bitbucket Server.

      Suggested Solution

      On start-up of FishEye/Crucible we should check if the environment variable GIT_SSH_COMMAND is set and prompt a warning to the user and or override with the usage of our own.

      Workaround

      Manually unset the variable GIT_SSH_COMMAND.

              Unassigned Unassigned
              mwilliams@atlassian.com Mark A.
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: