Once you add a Bitbucket Server Git repository to Fisheye, a push to the repository automatically triggers Fisheye to run an incremental index. You don't have to configure customized polling to detect new commits, or set up dedicated Fisheye web hooks in your Bitbucket Server instance. 

A Fisheye administrator only needs to set up an application link with Bitbucket Server for Fisheye to be ready to respond to 'refs changed' notifications published by Bitbucket Server. 

注意:

• Fisheye may not receive the notifications published by Bitbucket Server under some circumstances, for example if Fisheye is being restarted, or if there are intermittent network issues. Therefore, we don't recommend disabling polling completely, but that the polling period be extended to 2 hours or even 24 hours, so Fisheye can catch up with any missed events. See Updater.
• The automated notifications published by Bitbucket Server when new changesets are pushed to the repository do not cause polling to be disabled. Those notifications are meant to ensure any changes made to Bitbucket Server repositories are promptly indexed by Fisheye.

Note also that Bitbucket Server was formerly known as Atlassian Stash.

When Fisheye is integrated with Bitbucket Server, a Fisheye administrator can easily add Bitbucket Server repositories to Fisheye with a single click. Once added, the repository behaves just like a native repository in Fisheye, so your team gets all the benefits of Fisheye indexing, browsing and searching. Furthermore, the repository becomes available to Crucible (when integrated), so you can perform in-depth code reviews for changes in the repository.

For detailed instructions for adding a Bitbucket Server repository to Fisheye, see Adding an external repository.