-
Notifications
You must be signed in to change notification settings - Fork 74
use proxy env PROXY_HOST and PROXY_PORT automatically if defined #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Would this enable pipeline scripts to set the PROXY_HOST and PROXY_PORT environment variables and then perform access requests via the objects? |
We tested the PR with the |
How does this play with Jenkins' own support for configuring http proxies? It seems this information should be exposed to Plugin somehow |
This improvement is very handy because it will allow us to choose how to configure the proxy settings. |
This would be extremely helpful in systems with complex proxy settings and build nodes which each need different settings. |
I would also like to see this merged, I've tried the JVM workaround suggested in the original issue but, to no avail. Mentioning the original author + some of the contributors from recent releases to see if we can get an update on this: @luka5 @gounthar @xocasdashdash @LeoQuote @aaronjwhiteside Any help here would be greatly appreciated, thanks! |
Hi all, Does anyone have a hint how I can override/workaround this issue? I have the proxy configured in the global config of Jenkins. Thanks in advance! |
I managed to solve my issue by adding as option the proxy address to the command line that starts the Jenkis and works:
|
With this change, we will automatically use the
PROXY_HOST
andPROXY_PORT
environment variables, if defined.This is useful, in any environment, which requires a HTTP Proxy to communicate to the other endpoints. I built it locally, and it works for me.
Resolves #66
What do you think about it?