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
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
When trying to Release a change from AWS CodePipeline (we have an existing Bitbucket integration), we intermittently get the following error message below.
"Action execution failed
We received an update from our engineering team that the issue which is affecting the AWS CodePipeline integration feature is now resolved.
You can further check this incident here: https://bitbucket.status.atlassian.com/incidents/bckkpd21xrgg
We apologize for the inconvenience this has caused you and your team.
If you need more help, please do let us know.
Hi @Mark C , seeing the same issue on my end. I just setup a CodePipeline with BitBucket source. The Source stage worked fine on first launch right after creating pipeline. Once I committed a new change in BitBucket, Source stage reran and failed. Reverted to original source code and same issue. I think its related to the webhook and will troubleshoot that next. Just want to confirm issue is still present.
There's a few url redirects I've noticed when accessing target repo from project level in bitbucket webapp. It adds a redundant '/src/main/' to path. Not sure if this is new or has always existed but doesn't seem right.
Also, when I access the repo publicly with the https clone address provided, there's a pop up about credentials no longer needed (click OK) and lands me on what should be the repo address BUT without the redundant '/src/main/'. Reloading this page presents same error but once I add a '/' to end of url, shazam. It redirects through the redundant URL and correctly displays the repo.
Hope this helps. Hoping a fix is coming soon.
Hi, I'm experiencing the same issue just today. Please let me know if we have a way to resolve this on our end.
Just to be clear we did not change anything in our code pipeline configuration. The error bellow just suddenly popped out
[Bitbucket] Bitbucket returned an Internal Error exception. Please retry shortly. If the issue continues it may be reported on the Bitbucket status page at https://bitbucket.status.atlassian.com/
if you have your branch naming convention as feature/branch then bitbucket fails to redirect to URL like so
As of 16 January 2022, this bug still occur. Thanks to Frank DiRocco's advice, I solved it by setting code_build_clone_output as True in my CodeStar Connection.
code_build_clone_output=True, # Bitbucket fix