Mercurial repository error while detecting branches

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

A Bamboo Plan is configured with Bitbucket Cloud Mercurial repository and Automatic branch management.

The following always appear in the UI:

1 2 3 Project - Plan build : Repository error while detecting branches for plan PRO-PLA. command hg pull --config 'ui.ssh=ssh -o StrictHostKeyChecking=no -o BatchMode=yes' https://username:********@bitbucket.org/project/repo failed. Working directory was `/home/bamboo-home/xml-data/build-dir/_hg-repositories-cache/xxx'. stderr: abort: HTTP Error 400: Bad Request stdout: pulling from https://username:***@bitbucket.org/project/repo searching for changes

Cause

It is a bug with Mercurial as stated in https://bitbucket.org/site/master/issues/8263/http-400-bad-request-error-when-pulling

Resolution

Upgrade Mercurial to version 3.8.3 or newer.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.