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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Please add a Note to suggest not adding big binary files into Bitbucket repo.

Hi Experts,

I'm using both Bitbucket and Azure Devops. And I found that if I have big binary files in my repo(over 160MB), then I can't create Azure Devops Yaml pipeline from my repo any more, ikt always states:

"Unable to get the path contents from the Bitbucket repository 'mainincubator/lissi-edge' for the branch or source version 'master' and path ''. It is possible the specified path is a file. Error from Bitbucket: Request timed out after 5000ms"

So it occurs the Bitbucket blocks my request if my repo has big binary files. (I have specific reason to contain the binary files in repo)

Is it convenient for team to fix this issue? Or add a "Notes" in Bitbucket document to prevent other members from meeting same issue?

Please advise.

1 comment

Hi Team,

We are also blocked with this issue. Are there any alternate solution would help us while you working on it.

We are unable to create pipelines from azure devops for this repo.

I am also blocked by this... I have three binaries that I need in this repo, and I now can't connect it to azure pipelines. More annoying that it was working fine previously. 

Blocked as well for the same issues. Binaries are not very large but needs to be this way for the moment.

Was this resolved? Having same issue

We solved it by moving to github.


We are also facing this issue. 
Moreover, it is not possible to create a pipeline connected to bitbucket Repo with Azure DevOps REST API.

This is a pain if the solution is to move to another source control host service..

Yeah, that's what screwed us. We use Azure DevOps and just couldn't do anything with it. Transition to github has been pretty seamless for us to be honest. Especially if your build pipelines are in .yaml format.


I finally found a workaround for the issue of bitbucket not being able to scan my repository to find YAML files.

I have moved my pipeline in a branch where I do not have the binaries.
Then on the URL opened by Azure DevOps when it try to find the YAML file, you can edit the URL and modify the branch name.

--> My YAML files are successfully retrieved.

After saving the pipeline, you can use the Azure DevOps edit mode to select the appropriate branch for your YAML pipeline (usually master)


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events