Summary

As per Git Integration guide for Fisheye/Crucible:

When you add a Bitbucket Server repository to FishEye, a push to the repository will by default automatically trigger FishEye to run an incremental index. No further configuration is required – you don't have to configure polling for new commits, or set up dedicated FishEye web hooks in your Bitbucket Server instance.

Environment

Bitbucket Server 4.9.1
Applinks setup between Fisheye/Crucible using OAuth

Steps to Reproduce

1. Step 1
   Create OAuth between Fisheye/Crucible and Bitbucket Server
2. Step 2
   Add a Bitbucket Server repository as per the above guide
3. Step 3
   Push to the Git repository and check that the commit appears in Bitbucket Server and Fisheye/Crucible UI

Expected Results

Fisheye/Crucible triggers an incremental sync only when it detects a new commit in Bitbucket Server Git repository

Actual Results

Fisheye/Crucible logs indicate that it is still using the configured/default polling interval to trigger the incremental index:

2016-10-26 09:51:27,716 DEBUG [IncrPing1 blah1 ] fisheye RepositoryStatus-setMessage - Status change [blah1]: Getting updates from ssh://git@localhost:7999/blah/blah1.git
.
.
2016-10-26 09:51:37,720 DEBUG [IncrPing1 blah1 ] fisheye RepositoryStatus-setMessage - Status change [blah1]: Getting updates from ssh://git@localhost:7999/blah/blah1.git
.
.
2016-10-26 09:51:47,721 DEBUG [IncrPing1 blah1 ] fisheye RepositoryStatus-setMessage - Status change [blah1]: Getting updates from ssh://git@localhost:7999/blah/blah1.git

The default polling interval is set to 10sec as indicated by the incremental thread running every 10sec.

Workaround

None available yet.