Hi Curtis,
The long and short of it is that managing Jenkins behind a proxy isn't as
simple as managing it otherwise, for all the reasons you mention.
We configure our slaves via puppet, and deploy the proxy configuration
automatically. For docker containers, again we create base images which
include the proxy configuration and work from there.
Regards,
James
On Tuesday, 11 July 2017 20:25:34 UTC+1, Curtis Kline wrote:
>
> Hello all,
>
> I am setting up a new Jenkins server and some build nodes to replace an
> old one. The cloud instances running Jenkins jobs are behind a Squid proxy
> and cannot access the Internet directly. The initial problem of not being
> able to download any plugins was easily resolved by entering proxy settings
> in the Jenkins admin UI. I was able to get Linux shell commands working
> with a http_proxy environment variable. It's gotten pretty ugly from there,
> though.
>
> The Android SDK and Gradle build tools each had proxy settings. Docker
> containers need to be started with proxy settings. Java and SBT each have
> proxy settings. The HockeyApp plugin has a bug preventing use with a proxy.
> And it continues...
>
> Does anyone else run Jenkins behind a proxy server? Is it a maintenance
> nightmare? I'm beginning to think we are going to have to get the Jenkins
> instances out from behind the proxy or face ongoing maintenance headaches.
>
> Thanks,
> Curtis
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/f7372586-9ce7-407a-8b7b-0228f154e8d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
