On the agent (node) configuration page when configuring to "Launch agent
by connecting it to the master" there is an Advanced button. If you
click that, one option that becomes visible is "Tunnel connection
through". This *might* work for you. Read the inline help and try it to
see if it meets your needs.
Another thing that might work for you soon is the the upcoming WebSocket
connection mechanism (
https://github.com/jenkinsci/jep/blob/master/jep/222/README.adoc ).
Looks like it's currently targeted towards the next weekly.
Jeff
On 1/23/20 5:59 AM, Simon Richter wrote:
Hi,
I'd expect this to be somewhat obvious, but it doesn't seem to be: I have a
JNLP agent on a Windows VM that should talk to the Jenkins master on
another VM in the same network. The Jenkins master has a standard nginx
proxy before it to allow external requests to come in.
The agent now connects to the proxy, requests connection information,
receives the port number and connects to the proxy's IP address with the
port number it received from the master.
Obviously this fails because the proxy does not forward the internal agent
ports (these are not supposed to be externally visible).
Is there a way to let the Jenkins master hand out not only the port number
but also the correct IP address to agents (after all, being run behind a
proxy seems to be a very common use case to the extent that the public URL
is configurable)?
Simon
--
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/72c7c6fb-3eda-b508-748d-5b110a8bd722%40cloudbees.com.
