How do you customize Slack notifications?

[Deleted user]

We have integrated Slack with our Bitbucket pipelines however employees complain about the notifications being too chatty and also often not useful. I have had to temporarily disable it until we can clean this up.

IE: When a pipeline runs it reports to Slack the commit Hash and the user that committed that hash. Since we often run pipelines in some repos many times on the same commit, this is not useful. We would like to see the user who actually initiated the pipeline manually, the start and end times and basically nothing else to keep the communication clean.

If possible it would be icing on the cake if certain information from the pipeline output could also be posted to the channel. This would need to be highly customized though to again keep the communication slim and neat.

Thanks

[Philip Hodder]

Hi David,

Currently the following notifications can be set up:

• Pipeline failed
• Pipeline fixed (first successful pipelines on a branch after failing pipelines)
• Pipeline succeeded
• Deployment failed
• Deployment stopped
• Deployment succeeded

Which ones are you using at the moment? Perhaps you can remove a few notification types you're using to reduce the noise.

Currently we don't support configuring the content of the notification sent.

What's the use-case you have for running a pipeline multiple times on the same commit?

If you'd like you can open a feature request for the custom configuration, and trigger rules you'd find useful for Slack notifications.

Thanks,

Phil

[Deleted user]

We are using a mixture of all of these but primarily are concerned about Pipeline failed/succeeded.

In Slack we would like to see the user who actually initiated the pipeline manually, the start and end times and basically nothing else to keep the communication clean.

[Deleted user]

Is this still not possible? Seems like a simple text field.

[Philip Hodder]

@[deleted] at this stage I recommend you use our Slack Pipe inside of an after-script.

[Anand Kumar]

@Philip Hodder  we would like to see the user who actually initiated the pipeline manually through slack. kindly help for a solution ASAP.

@[deleted] -KUDOS  that you have already raised this question  4 years before, yet no solution.