I am trying to connect mercurial repos to fisheye. The server that mercurial is running on is using a self-signed certificate for serving the mercurial repositories, and when I try to add the repo in fisheye (using password for https authentication and supplying the fisheye admin password for this), and testing the connection to the repo I get the error message:
Error testing connection.
Non-zero exit code: 255
As far as I can see, everything is configured correctly.
Mercurial appears to be configured correctly
Mercurial executable (hg) = /Program Files/TortoiseHg/hg.exe
Does the stack trace above point to anything useful I could try next?
I finally managed to solve this (at least, partially).
The repository I tried to configure in Fisheye contained couple of thousand files!
After removing those (also from the history, by using the 'convert' extension of mercurial), I was able to clone and index the repository.
I hope this helps someone.
This might help (though not really making sense to me).
After several failed attempts to Test the connection, I just saved the configuration.
As mentioned, there was no indexing happening, as the indexer just stuck at the first commit.
I did "Re-clone and Re-index:" in the "Maintenance" menu, and all of a sudden the indexer started...
a quick search using the stack trace lead to this issue:
It suggests that while the test connection reports a failure, actually adding/saving the repo results in correct indexing. Could you try adding the repos despite the failed tests and check whether they begin indexing?
Have you guys ever figured this out? I have a similar (same?) problem while testing a newly added mercurial repository.
The error message in my case:
Error testing connection.
process timed out
If I ignore the error and just Save the settings, the repository clone is at the first changeset:
Indexing commit 8ebd8aaa9bfc5e469a1ff5fce93c9c8bebd3ce80
The "Test" under "SCM details" for other repositories that were added sooner, works fine. No timeout, but "Connection succeeded".
If I clone the repository manually on the Fisheye server (windows command line) with the same username and password, it works. So it must be the Fisheye front/backend, in my opinion.
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events