How to configure Bamboo Agent to connect to Blackduck application through outbound proxy
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
Summary
This article shows how to configure Bamboo Agent to connect to Blackduck application through outbound proxy.
Environment
The solution in this article has been tested on version Bamboo 8.0.4 but may work with other versions of Bamboo
Diagnosis
When running the build it shows that the agent was unable to connect to Blackduck application
1
2
build 19-Jul-2022 05:07:42 2022-07-19 05:07:42 EDT ERROR [main] --- Could not perform the authorization request:
Connect to <blackduck-server> [<blackduck-server>/<blackduck-ip>] failed: Connection timed out: connectBamboo Agent is configured to connect to an outbound proxy
1
2
3
4
5
6
wrapper.java.additional.1=-Dbamboo.home="<bamboo-home>"
wrapper.java.additional.2=-Dbamboo.agent.ignoreServerCertName=false
wrapper.java.additional.3=-Dhttp.proxyHost=<proxy-server>
wrapper.java.additional.4=-Dhttp.proxyPort=<proxy-port>
wrapper.java.additional.5=-Dhttps.proxyHost=<proxy-server>
wrapper.java.additional.6=-Dhttps.proxyPort=<proxy-port> Cause
Build logs that Blackduck application is not loading the proxy parameters
1
2
3
4
5
6
7
8
9
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- blackduck.trust.cert = TRUE [cmd]
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- blackduck.url = <blackduck-app-url> [cmd]
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- detect.bom.aggregate.name = <aggregate-name> [cmd] *** DEPRECATED ***
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- detect.code.location.name = <location-name> [cmd]
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- detect.detector.search.depth = 3 [cmd]
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- detect.project.name = <project-name> [cmd]
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- detect.project.version.name = <version-number> [cmd]
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- detect.source.path = <build-path> [cmd]
build 27-Jul-2022 09:43:30 2022-07-27 09:43:30 EDT INFO [main] --- logging.level.detect = DEBUG [cmd] Solution
Configure your Black Duck connection properties file to enable proxy connection
1
2
3
4
5
6
7
8
9
10
11
12
13
# suppress inspection "UnusedProperty" for whole file
# BlackDuck credentials
blackduck.url=
blackduck.username=
blackduck.password=
blackduck.api.token=
blackduck.timeout=120
blackduck.proxy.host=
blackduck.proxy.port=
blackduck.proxy.username=
blackduck.proxy.password=
blackduck.trust.cert=falseWas this helpful?