Stash commit notifications to fisheye/stash

We're currently using Stash 3.3 and have recently upgraded our fisheye/crucible server from 3.1.8 to 3.6.1 in the hope of getting the OAuth integration working between Stash and Fisheye to allow commit updates to be automatically pushed from Stash.

The upgrade went smoothly (thank you Atlassian) and the OAuth Application Link between the two servers has been setup. From within Fisheye/Crucible we're able to see all the repositories that are in Stash and add them. Our existing repositories that were in Fisheye/Crucible show that they have been 'ADDED' via the 'Stash' tab in the Repositories section of the administration tools. Despite this commit updates are still only happening when our hourly poll occurs so it seems the Stash notifications as advertiesed ( are not happening.
All documentation around the integration simply say it should just work once the Application Link is setup.

I've looked through Stash and on the Administrator account profile it shows 'FishEye and Crucible' as being authorized applications at around the time I enabled the OAuth between the two apps.

Has anyone else had any issues similar to this? Could it be something to do with the repositories existing prior to the OAuth link being created or have I missed something else entirely? 

1 answer

1 accepted

0 votes
Answer accepted

After contacting Atlassian support we were suggested to install Applinks Diagnostics Plugin on both our Stash and FishEye/Crucible services and perform the diagnostic tests.

The test revealed an authentication issue. Removing the OAuth link and recreating it on both the FE/CRU and Stash ends and then approving the authentication on both ends resolved the issue.

I assume that reconfiguring an OAuth application link after upgrading out FishEye/Crucible instance didn't create the link properly. It would be nice to have this kinda diagnostic check performed during the linking and reconfiguring of apps.

Very happy to have this resolved. Thank you Atlassian Support. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder :  #!/bin/bash source "$(dirname "$0")/" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables ROLLBAR_ACCESS_TOKEN...

206 views 0 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you