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.
Hi,
I have setup a simple pipeline which is building and passing, although within sourcetree I am not seeing the build status or any status at all, just a grey dot. Although on sourcetree next to my commits am seeing that they are building correctly.
Where am I going wrong, my sourcetree is up to date.
Many thanks
Hi @richard_howse,
Do you have your Bitbucket added in Sourcetree?
If not, please add it in Preference Window - Accounts tab. Also, if you are using basic auth, please select http for protocol. We cannot pull pipelines status with ssh protocol using basic auth password. If using OAuth, protocol doesn't affect.
Thanks!
Hi, I'm facing this same issue. I have my Bitbucket account liked via OAuth + SSH. I have two repositories with pipelines set up, but the build status shows up for just one of them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you mind adding some screenshots?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure -- here are two repositories from the same Bitbucket Account, same permissions, both with pipelines enabled, both using SSH. Do you need screenshots of anything else?
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.
One year later and I have a lead on this issue. I noticed that clicking "View Remote" did not take me to Bitbucket, but to the url of some other remote that we also use (e.g. Heroku or AWS Codecommit). By removing all other remotes and leaving only the Bitbucket one, the build status shows up. I have not found a way of setting that remote to somehow stay as the primary one after adding the other back, other than renaming it to "origin".
Essentially, the build status only works when the Bitbucket origin is either the only one, or it is called "origin"
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.