Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Git repo Indexing is timing out

Jonathan Goldberg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 16, 2011

We are trying to evaluate fisheye and crucible but we are unable to index our main repo.

We don't really care about the history from 3 years ago that this repo has, but we care more about the ongoing commits so we can use it for code review.

Is there any way to configure the scan in such a way?

Thanks,

Jonathan

This is the error that we are getting:

Repository index failed due to error com.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.utils.process.ProcessException: While executing: "git whatchanged --always --reverse --date-order -m --no-abbrev --no-renames ad682c58f5f140a5c195abeba47a1b8027cc3e0b..066bda4d282b8bc9bdd59f4b7124dced81dba5ce --pretty=format:C:%H%nP:%P%nA:%aN%nE:%aE%nR:%cN%nF:%cE%nD:%at%nS:%s%nB:%b%n@@fe_body_end@@ " com.atlassian.utils.process.ProcessTimeoutException: process timed out


1 answer

1 vote
Gurleen Anand _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 21, 2011

Hi Jonathan,

The error indicates that the process is timing out before being able to complete the command:

"git whatchanged --always --reverse --date-order -m --no-abbrev --no-renames ad682c58f5f140a5c195abeba47a1b8027cc3e0b..066bda4d282b8bc9bdd59f4b7124dced81dba5ce --pretty=format:C:%H%nP:%P%nA:%aN%nE:%aE%nR:%cN%nF:%cE%nD:%at%nS:%s%nB:%b%n@@fe_body_end@@ "

Please check how long this command takes to complete via the command line and increase the value of the "Command Timeout" property for your Git repository:

http://confluence.atlassian.com/display/FISHEYE/Git

The default is "1hour".

If the problem persists, please contact Atlassian Support: https://support.atlassian.com for further investigation.

Thanks,

Gurleen

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events