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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Fisheye doesn't register Stash commits automatically

Per BSERV-4031, I expect Fisheye 3.8.1 to be automatically notified of git commits from Stash 3.7.1, but it is not. Repositories are indexed and Fisheye is otherwise mostly working (it seems to be ignoring .mailmap, but that is likely unrelated). The repositories are all using ssh:// URLs and were added via the "Stash repositories" tab. I selected "disable polling" in Defaults->Updater for "non-CVS repositories". No errors are logged, and I'm not sure where to look to further figure out what is broken.

4 answers

1 accepted

1 vote
Answer accepted

This is a known bug being tracked here:

Note: Stash is now called Bitbucket Server, hence the issue key is BSERV, but the issue above was discovered in Stash.

0 votes

Hi @Gordon Pettey,

You may want to contact our Support Team via, that way we would be able to collect more information about your configuration and analyse it thoroughly. 



Hi Piotr, We are having the same issue. We are running Crucible 3.8.0 with Stash 3.11.2. I'll contact the support team too.

Yes, there is a working (AFAICT) app link (hence the repositories added to Fisheye via the "Stash" tab). Enabled debug logging on Fisheye and Stash. After commits and push, Stash logs nothing. Fisheye doesn't log anything about indexing, but it shows "fisheye ProfilingServletFilter-logRequest - start request GET rest/remote-event-consumer/1/capabilities nosession" after each push.

0 votes

Hi @Gordon Pettey,

Just to double check, do you have application link set up between FishEye and Stash?   Once the link is configured Stash should be sending remote notifications to app-linked FishEye/Crucible instances each time new changes are pushed to any of its repositories.  Please confirm the application link is set up correctly please.

Once this is enabled, each time Stash repository is updated and matching repository is found on the FishEye side, you should be observing debug messages in your FishEye instance like this:

Incremental index triggered for repository XXX

please enable DEBUG logging in FishEye (Admin / Global Settings / Server), push some changes to Stash repository that is being indexed in FishEye and check if you see such messages in FishEye's log.

Hope that helps,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their  Jira Cloud instance.  ...

549 views 15 18
Read article

Community Events

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

Events near you