I recently upgraded our self hosted Bitbucket server to version 6.10.1. After doing so, I noticed our Slack integration had stopped working. While debugging, I found that an official Slack integration plugin had been created since I had implemented a web-hook workaround a couple years ago. I have installed the official slack Integration plugin and set it up using the keys provided by the Bitbucket Server app in our Slack app directory. For whatever reason however, I am not seeing notifications appear in our Slack channel for subscribed repositories.
Oddly enough though, when I subscribe a repo to the Slack plugin, I.E. telling it to send notifications about that repo to a specific Slack channel, in that channel I get a notification from the Bitbucket_Server bot user that the connection has been made for that repo.
Hey there, welcome to the Community and thanks for using Bitbucket!
Some extra configuration is needed to get the Bitbucket Server integration working well if you're behind a firewall or in a restricted VPC (if you're in AWS). Details are available here for the extra steps necessary to get the integration working. It sounds like at least some of this is working, as you mentioned the integration is at least sending a subscription message to Slack.
After checking the configuration with the instructions above, you can also enable DEBUG logging for the following packages to get more helpful error messages in your server logs:
com.atlassian.plugins.slack
com.atlassian.bitbucket.plugins.slack
If you continue to see problems, we're happy to help! The output from the logs will be useful in seeing what's happening on the Bitbucket Server end of the connection.
Thanks!
Daniel | Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.