You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey there, I'm new to Bitbucket Pipelines, and am trying to see if I can duplicate my Jenkins pipelines' functionality with a pipeline on Bitbucket.
I've got a pipeline running, but I can't seem to get it to notify us when it's finished running.
Here's what I'm trying to do: update a Teams channel when a pipeline build has started or completed. When it's completed, I'd like to post its build status. That's it. Nothing fancy.
Here's as far as I've gotten:
Any ideas what steps I might be missing? I'm on Bitbucket Cloud, btw.
I found the solution myself, albeit a very basic one: set this up as an item in the "script" portion of after-script:
- curl -H "Content-Type: application/json" -d "{'text':'Hello World'}" https://<WEBHOOK URL>
Here's why I got snagged up: I was following the Microsoft docs for formatting the -d argument, but was getting a linting error in 'text': 'Hello World' because VS Code's linter, the Redhat YAML extension, was seeing the space after the colon in that payload and was barking about me trying to submit YAML. I removed the space, the barking stopped, the notification happened.
Now I get to go down the fun rabbit hole of string interpolation and passing variables inside single quotes, which bash hates.
Update: Thank you @inger_klekacz the issue was with space after "Content-Type:
Hi @inger_klekacz am trying to do the same thing, from normal terminal if I use this
curl -H "Content-Type: application/json" -d "{'text':'Sample msg'}" <WEBHOOK_URL>
It works notification happened.
but If I use
script:
- curl -H "Content-Type: application/json" -d "{'text':'Sample msg'}" <WEBHOOK_URL>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
please I’m trying to implement this as well into my pipeline. I will like to connect with you and see how you achieved this please. Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Below is the pipeline that you could use that worked for me
# MS TEams Notification
image: atlassian/default-image:3
pipelines:
default:
- parallel:
- step:
name: 'MSTeamsNotification'
script:
- echo "Teams Bitbucket Pipeline Notification...from Nataraj.."
- curl -d "{\"text\":\"Message from Bitbucket Pipelinedata...\"}" -H "Content-Type:application/json" $TEAMS_WEBHOOK_URL
Thanks,
Nataraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you could use the below command line
- curl -d "{\"text\":\"Message from Bitbucket Pipelinedata...\"}" -H "Content-Type:application/json" $TEAMS_WEBHOOK_URL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @inger_klekacz ,
You can use Microsoft Teams Bitbucket Connector. There is a short guide on how to set it up, but otherwise it is pretty simple.
If you have any questions please feel free to reach out.
Regards,
Leo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That was my first attempt, but it seemed like it supported everything except build status, which is basically the only thing I need right now. BTW when I was trying to figure it out, I clicked on the Support > Documentation link from the Marketplace link you posted, and the docs link was a 404. Thanks anyway, though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@inger_klekacz thanks, actually that's also what we need. From what I can tell the connector simply handles notifications globally around repository operations whereas we needed custom notifications issued from within pipelines on a per step basis.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tried the Microsoft Teams Bitbucket Connector a year later (2/2022) but it still does not support pipeline events.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the comment.
The Bitbucket does not send pipeline events to 3rd party apps. You can get notifications for commit status update events. This blog post could be useful.
If you could elaborate what you are trying to do - We can see if we can improve our Microsoft Teams Bitbucket Connector to serve you better.
Thanks,
Leo | Move Work Forward
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.