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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Fisheye com.cenqua.fisheye.rep.RepositoryClientException

Repository paused due to error com.cenqua.fisheye.rep.RepositoryClientException: java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E150000: 'https://svnurl/trunk' does not exist in revision 6,764 java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E150000: 'https://svnurl/trunk' does not exist in revision 6,764 org.apache.subversion.javahl.Cli

1 answer

0 votes
Themis
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 11, 2018

Hi there,

The article  Errors When Trying to Add or Index a Repository - non-existent in revision may be relevant in your case! It offers three potential causes with their respective solutions.

We hope one of them will work for you!

Best,

Themis

@Themis I solved the above problem by changing SVN URL from https://rootpath/projectname/trunk to https://rootpath/ and adding projectname in the path.

 

Now i am facing another issue. The indexing process is taking a lot of time, it started indexing yesterday (April 10,2018) at 11:00 PM UTC and only indexed 5.7% as of (April 11 ,2018 10:00 PM UTC). Please let me know.

Themis
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 12, 2018

Hi,

glad that the initial problem is solved!

As for long indexing times, it is not unexpected that the initial scan and indexing of a repository takes a long time, depending on the size of the repo, and the size of the changesets. 

Having said that,  it seems you are using the https protocol, which is slower compared to svn: or file: You can consider mirroring your repository locally to be able to access it with the file:// protocol. You can find more information here to improve the Fisheye scan performance.

Also, here are a few more resources that may help you troubleshoot slow svn indexing:

Hope this helps!

Best,

Themis

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events