@Robert Mao that is a good point. It shouldn't be hard to handle notification directly from your build scripts. The one downside to this though is you would have to build in handling of reporting the success/failure directly instead of having bitbucket do it for you automatically. Still though, your suggestion would be a workaround for the time being.
- gulp build || (c=$?; sh notify-slack.sh failed-build; $(exit $c))
- gulp publish || (c=$?; sh notify-slack.sh failed-deploy; $(exit $c))
- sh notify-slack.sh
But this is not ideal, because it forces every repository to have a copy of this script and the YML is not so clean with the "||" everywhere. Being able to select Pipelines in the triggers of a WebHook would be great:
@xtjhin, This doesn't feel resolved to me. I'm going to try out your snippet, however there is no way to currently just get failed notifications with the official bitbucket slack integration. When you get success and failed notifications, that's a lot of extra noise in your channel, when all you really care about is the builds that fail.