-
Bug
-
Resolution: Fixed
-
Low
-
6.9.1
-
None
-
Severity 3 - Minor
-
Issue Summary
When Bamboo is configured to use an outbound HTTP(S) proxy, whenever a Bitbucket Server-type repository is being added or edited in Bamboo, Bamboo is unable to obtain a list of Bitbucket Server mirrors, thus forcing the user to choose the primary mirror.
Environment
Bamboo with outbound HTTP or HTTPS proxy, Bitbucket Server with Smart Mirrors.
https://confluence.atlassian.com/kb/how-to-configure-outbound-http-and-https-proxy-for-your-atlassian-application-834000120.html
https://confluence.atlassian.com/bitbucketserver/smart-mirroring-776640046.html
Steps to Reproduce
- Create or edit a Bitbucket Server repository
- Go to advanced options
- Try to select a Bitbucket Server mirror
Expected Results
The mirror is available and can be selected.
Actual Results
No mirrors are available, except for the primary server.
The below is logged if log level DEBUG is set for package com.atlassian.bamboo.plugins.stash:
[BitbucketSeverMirrorClient] Error connecting to mirror: <mirrorName> [BitbucketSeverMirrorClient] java.lang.UnsupportedOperationException
Notes
Without the outbound proxy, system behaves as expected.
Workaround
Use primary BbS server or disable outbound HTTP(S) proxy.
- mentioned in
-
Page Failed to load