Open CarlInglisBJSS opened 3 years ago
On suggestion which has arisen; is the DNS lookup for the host and proxy being done on the worker node or the leader?
If the latter, then that's what's causing the problem as the worker and the leader are in different VPCs with different DNS Zones.
Jenkins version: 2.289.1 Plugin-version: 1.42
Problem: Trying to use
s3DoesObjectExist
through a proxy is not working due to an error resolving the proxy by hostnameBackground: I have developed a number of pipeline processes which have worked fine with our transparent proxy (i.e. not needing to set the http_proxy etc. group of environment variables). For reasons involving another project our jenkins workers are now going to be behind a client proxy (i.e. setting those environment variables).
I had hoped that I would be able to just set the environment variables and all would be well, however that's turned out not to be the case.
Bucket name and other identifying marks are redacted for client confidentiality reasons.
Result of
set | grep -i http
(snipped to just relevant entries)Using
aws s3
via sh to show connectivityActual error including stacktrace
What I've tried:
squid
instead of the FQDN - same issue but does resolve in ansh
step.
s - same issueI'd appreciate any thoughts on what else I can dig out and/or try as I really don't want to have to rewrite everything I've done with this plug in to use
sh
calls.