Cloud build fails to clone from mercurial repository on bitbucket

Unity Services
1

Hello,

It has been doing this since yesterday. I have checked multiple times that the repo URL, username, and password are correct.

Looking at line [quote]
12: java.io.IOException: Cannot run program “/bin/bash” (in directory “/BUILD_PATH/”): error=2, No such file or directory
[/quote] it seems that it is for some reason not finding the bash shell to run the hg commands on, or the directory to run them in.

2

Hi there,

Can you please direct message me a link to your project in Cloud Build?

3

Link sent via direct message. Thank you for looking into this.

4

I’m having the same issue. It worked okay for a while, but hasn’t been able to build for the past two weeks.

5

Has there been any progress on this? Cloud Build really isn’t useful to us if we can’t build for iOS anymore.

6

I haven’t yet heard anything back from unitychrism since I sent the link via direct message…

7

Got it working!

unitychrism told me that the reason for the error really is that the mercurial (bitbucket) authentication fails.

So I tried re-entering the credentials again, and it still failed the same way. Then I created a new bitbucket account and gave it read access to the same repository and entered those credentials. Now it works (well the build still fails, but now it is just because of an automatic version numbering script I have that has a bug in it).

I have a hunch on what might have been wrong with the bitbucket account that didn’t work. The password of the user account that didn’t work had lots of special characters in it. The password for the new one has only alphanumeric characters. It might be that Unity Cloud Build can’t handle all the special characters that bitbucket passwords can have.

Thank you unitychrism for your help! (already sent you almost this same message as direct message).

8

Hi,

Cloud Build has started doing this again. Not every time I build though, just most of the time.

The credentials have stayed the same so it is not about those this time.

I have made more build configurations since last time. Some are for our release branch and some for development. There is also a problem there. For some reason the builds configured to build from the development branch build from the release branch instead.

Here is the error log for a failing build:

I am sending this same as a direct message to unitychrism (with repository links and passwords etc.) so he can take a look at it again.