-
Type:
Bug
-
Status: Resolved
-
Resolution: Done
-
Affects Version/s: 2.5.1
-
Fix Version/s: 2.6.0
-
Component/s: None
-
Labels:
-
Environment:
-Jenkins Artifactory Plugin: 2.5.1
-Jenkins: 2.10
-Artifactory: 4.9.0
-The Jenkins master, as well as the slaves and Artifactory itself are running inside docker containers. Jenkins master container has its own host, slaves another host, and artifactory another host.
-Docker version: 1.9.1. Hosts: RHEL 7.2.-Jenkins Artifactory Plugin: 2.5.1 -Jenkins: 2.10 -Artifactory: 4.9.0 -The Jenkins master, as well as the slaves and Artifactory itself are running inside docker containers. Jenkins master container has its own host, slaves another host, and artifactory another host. -Docker version: 1.9.1. Hosts: RHEL 7.2.
This bug is simillar to the bug reported on HAP-712 , but I'm using Jenkins pipeline with Groovy DSL. The flag "Bypass HTTP Proxy" is checked on Artifactory server definition inside Jenkins system configuration, but it appears flagged to false when I access the server from inside the pipeline Groovy script.
As a workaround, I flagged bypassProxy to true manually:
def server = Artifactory.server('artifactory_server')
server.setBypassProxy(true)
Jenkins: 2.10
Artifactory: 4.9.0
Jenkins Artifactory Plugin: 2.5.1
