Bamboo Cloud error while detecting branches for plan

[Chris Phillips]

I have a build plan that's running fine for our "default" branch but never detects new branches even though I have selected "Create plan branches for all new branches" under "Automatic branch management".

The error log shows an error like this, hundreds of times:

Repository error while detecting branches for plan MYPLAN. com.atlassian.bamboo.plugins.hg.HgCommandException: command /usr/bin/hg pull --config 'ui.ssh=ssh -o StrictHostKeyChecking=no -o BatchMode=yes' https://MY-USER:********@MY_REPO failed. Working directory was `/data/jirastudio/bamboo/home/xml-data/build-dir/_hg-repositories-cache/c66398d56b8a4bc204aa182e9c43e6201243afc6'. stderr: abort: HTTP Error 400: Bad request
 stdout: pulling from https://MY_USER:***@MY_REPO
searching for changes

If I run the exact hg command from my machine, it successfully pulls the repository from our remote provider.

Any suggestions on getting this to work? Automatic plan branches are literally one of the key reasons we're even looking at Bamboo.

[Chris Phillips]

For reference, I also submitted this as a support request: https://support.atlassian.com/servicedesk/customer/portal/23/JST-157606

[Bruno Rosa]

Chris, I was looking at your support request and I noticed that you were able to sort things out. I think it might be a good idea to post the answer here to help other users that might be facing the same problem. Feel free to give a more detailed response about what happened.

For anyone else out there looking at this article, we found other articles in reference to HTTP 400 errors with mercurial when a proxy or firewall is involved and potentially manipulating or blocking the requests being made. Make sure to double check that. For this case it turned out to be a problem with too many topological heads in the repository, resulting in large HTTP requests. Also a good idea to keep that in mind if you're having similar problems.