Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Not able to connect to Bitbucket from AWS CodePipeline

When trying to initiate a deployment from Bitbucket I am getting an error message as "Action execution failed[Bitbucket] Bitbucket returned an Internal Error exception. Please retry shortly. If the issue continues it may be reported on the Bitbucket status page at" from code pipeline.

I am facing this issue from last few hours only

8 answers

I have caught this issue too recently. 

I'm still have the same problem

Hello, I have the case BBS-178577 with the same problem, it is still under review

hello. I have this issue right now... Did you find how to solve this?? thanks

it is happening to me too. and I have no solution for now.

Like # people like this

It's happening to me as well but with Single repo. Working for other repos on same account with same codestar connection.

Like Smart Dev likes this

Could Atlassian could take a look at it ASAP? it is blocking our pipeline process.

Like # people like this
Like Smart Dev likes this

Finally they updated status page for issue.

I've been having this issue way to much for quite some time now

I was able to resolve this by ensuring the code pipeline source stage does a FullClone rather than the default "CodePipeline default"

The issue just occured to me too. 

Did you find out what caused this issue? I have had this for the first time today but only on one repo

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events