Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Any ways to improve pipelines notifications on slack?

The PR create/merge notifications on slack are nice, they contain all the relevant information i.e. source branch, destination branch. But the pipelines message lacks sufficient information to get all the necessary details.

The slack notification looks like:

Deployment to <deployment name> successful. (Pipeline #106)
<commit ID> Merged in DS-358 (pull request #341)


Here, it should say the branch on which the pipeline ran, but the message rather says the last merged message.
My setup have dev, stage, prod branch which connect to my dev, stage prod clusters. The branch name on which I am running the pipeline is needed in the slack message.



0 answers

Suggest an answer

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

📣 Calling Bitbucket Data Center customers to participate in research

Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...

118 views 2 4
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you