Error
Hi Viachaslau,
This is actually a little bit different of what I was looking for. I searched for something related to this and, based on the log, it is possible you are facing the bug described by https://jira.atlassian.com/browse/FE-4335. Can you please confirm if you've set any include/exclude path for this repository? If this is the case, I would suggest removing the include/exclude paths defined, or adding this same repository (with a different name) without setting the include/exclude path for testing purposes, in order to see if it will be indexed.
If this is not the case, please consider the suggestion of opening a support ticket at https://support.atlassian.comfor a further investigation on this.
Viachaslau,
In addition to Felipe's words, as you said that from the command line you are not getting any errors, it is also possible you are facing the bug described by https://jira.atlassian.com/browse/FE-4926.
In order to check this, I suggest you to look into your logs for a WARN containing a message "Parent not found". If this is the case, looking into the parent commit indicated, you might see double quotes in the files of this commit, which would cause FishEye to fail processing it. This should confirm this is the issue.
Please notice this is fixed since FishEye 3.1.5, so an Upgrade would solve this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thnak you all.
I tried to re-index from scratch,but that does not help.
I am using 3.4.0 version.
WARN message contains "Cannot resolve changeset parent id cdd39425cc664b656d07ac8840199a7170ab9488 for changeset c535e907c7a233cd9931157da412f0e7751cb83a in REPO-NAME". Gustavo,is that what you mean?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Still seeing FE-4926 in 3.10.1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Viachaslau,
It looks like the caches in this repository have become corrupted someway. Would it be possible for you to re-index this repository from scratch?
It might be that the repository URL and/or path defined in FishEye are incorrect.
It might also help increasing the Operation Timeout setting.
Please also check that your Git version is among the supported versions for FishEye.
I hope this helps!
Kind regards,
Felipe Kraemer
Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.