Upgrading Bamboo to 5.15.3 Breaks Plan Branches Using Repository Authentication Type 'Username and Password'

Summary

Bamboo build plan branches are failing to authenticate successfully after upgrading Bamboo to 5.15.3.

Environment

• Bamboo 5.13.0.1 and 5.15.3
  • Most likely affects all versions < 5.15.X and upgrading to 5.15.X

Steps to Reproduce

1. Install Bamboo 5.13.0.1
2. Set up Mercurial and Git repostories with 'Username and Password' for authentication
3. Configure builds for the repositories and set up automatic plan branch configuration.
4. Create a couple plan branches and observe Bamboo automatically builds them successfully.
   • The plan branches will be configured with 'Override the plan's default repository settings' enabled.
5. Stop Bamboo 5.13.0.1
6. Upgrade Bamboo to 5.15.3
7. Attempt to run the plan branches.
   • You can also go to test the connection of the repository for the plan branch to reproduce similar error.

Expected Results

Expect the plan branches to run successfully.

Actual Results

The plan branches fail to run due to authentication errors with the configured username/password.

The below exception is thrown in the atlassian-bamboo.log file:

2017-03-20 20:47:36,937 INFO [9-BAM::PlanExec:pool-16-thread-1] [RetryingTaskExecutor] Task 'Detecting branches HG' was unsuccessful. Run 1 / 2. Exception thrown when running task 'Detecting branches HG', with message: command /usr/local/bin/hg pull --config 'ui.ssh=ssh -o StrictHostKeyChecking=no -o BatchMode=yes' https://*** failed. Working directory was `/Users/mduong/atlassian/bamboo/bamb51301/data/xml-data/build-dir/_hg-repositories-cache/885513b01063a0687a3056cba9259fbbaada78ba'. stderr: abort: authorization failed
 stdout: pulling from https://*****
...
2017-03-20 21:34:11,943 INFO [9-BAM::PlanExec:pool-16-thread-3] [DefaultErrorHandler] Recording an error: Unable to detect changes : PRJ217934-PLN179346 : command /usr/bin/git ls-remote https://***** failed with code 128. Working directory was [.]., stderr:
remote: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile.
fatal: Authentication failed for 'https://*****'

Workaround

Disable the 'Override the plan's default repository settings' setting for the source repository of the plan branch.