No candidate revisions, bitbucket private repo

Having issues with setting up cloud build for a private bitbucket repo. Full build log looks like this:

1: Running Prebuild steps
2: done.
3: bvr 0.2.41
4: bvr-api 0.0.40
5: Using strategy: Default
6: Cloning the remote Git repository
7: Cloning repository git@bitbucket.org:darqwan/blobbie-platformer.git
8: git --version
9: git version 2.2.1.62.g3f15098
10: Fetching upstream changes from origin
11: No candidate revisions
12: ERROR: Couldn’t find any revision to build. Verify the repository and branch configuration for this job.
13: postbuildstatus finished successfully.
14: ls: /BUILD_PATH/blobbie-platformer-627d9b00-9e2d-6f25-3ae3-8f652c943194.551ee95f64b2ee6d55316d6c.default-web/.build/cache: No such file or directory
15: Deleting project workspace…
16: Finished: FAILURE
Status: FAILED

I’ve added cloud builder’ ssh public key to my bitbucket account. I’ve tested the availability of the project with another clone made using my own public key, project is clonable (using the branch configuration specified in project’s settings) and compilable. Any online references somehow point to CI scripts from hudson/jenkins (that are probably reused in unity cloud build) and not something I could consider in my setup.

Also, is it possible for Unity team to consider applying the 1 build/60 minute only for working builds in the free tier (and the paid ones)? Its very frustrating to not be able to test potential fixes for these kind of problems without deleting the project (or waiting for an hour, which is completely not acceptable). I personally expect this would improve the adoption rate: less frustration, more adoption.

UCB seems to be picky about branch names, even though the branch name was properly selected, unless it was named master it didnt work (or some planets have aligned in the mean time).

What kind of branch names did not work? So far I had no problems with different branches on bitbucket.
Yes, we evaluate those kind of ideas!