Public URL and node communication configuration

[Antonio Fernández Vara]

Hi all,

We are running jenkins using marathon, so we get some random port (over 31000) for out master. If jenkins url points to that ip and port all works perfectly.

We are configuring now the public url of the site, so Jenkins URL must point to the url to generate correctly mails and Google Oauth plugin configuration, but after the change jenkins slaves fails since they are trying to reach the public url at some not exposed ports.

Where we must configure that 'private url' to tell slaves how to reach the correct url? After review documentation we are not able to find a solution. Reviewing a Jenkins issue (https://issues.jenkins-ci.org/browse/JENKINS-11982) we are lost too.

Tryed configuring jnlp settings too but seems we are doing something wrong.

-jnlpUrl http://10.10.10.10:31438/computer/${NODE_NAME}/slave-agent.jnlp

Thanks in advance.

[Manivannan]

Recent feature (https://github.com/jenkinsci/mesos-plugin/pull/92) which allows you to configure absolute url locally to mesos plugin so that you can configure public URL / reverse proxy URL for Jenkins.

This feature is yet to be released. Can you build the plugin from master branch and try it? 

--
You received this message because you are subscribed to the Google Groups "Jenkins Mesos Plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-meso...@googlegroups.com.
To post to this group, send email to jenkin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-mesos/e9dfa3ff-ce8d-4339-b8fa-52ea3bf3c35c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Antonio Fernández Vara]

Will try that and use it until next release.

Thank you so much.

[Brian Henderson]

Hi, I'm setting jenkinsURL, but how do I set the jnlp url?

the mesos-slave-agent.jnlp.jelly in the PR has a section for setting the tunnel configuration, but I can't figure out how to set this through the mesos plugin.

thanks,

[Vincent Latombe]

There are two things involved here :

* The url to the jnlp file. In most cases setting the Jenkins URL through the global settings will set that right. To be honest I don't know when the field exposed by the mesos plugin has a valid use.

* The host and port to connect to Jenkins through jnlp. It may not be the same host as the one used by Jenkins URL. You can override these through system properties if you are doing port forwarding or reverse proxy.

See https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/TcpSlaveAgentListener.java#L296

-Dhudson.TcpSlaveAgentListener.hostName=myinternalhost

-Dhudson.TcpSlaveAgentListener.port=123

Vincent

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-mesos/81ad6a1e-c00d-4237-a90a-e69419ac5216%40googlegroups.com.

[Vincent Latombe]

There are two things involved here :

* The url to the jnlp file. In most cases setting the Jenkins URL through the global settings will set that right. To be honest I don't know when the field exposed by the mesos plugin has a valid use.

* The host and port to connect to Jenkins through jnlp. It may not be the same host as the one used by Jenkins URL. You can override these through system properties if you are doing port forwarding or reverse proxy.

See https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/TcpSlaveAgentListener.java#L296

-Dhudson.TcpSlaveAgentListener.hostName=myinternalhost

-Dhudson.TcpSlaveAgentListener.port=123

Vincent

2016-03-21 21:58 GMT+01:00 Brian Henderson <servin...@gmail.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-mesos/81ad6a1e-c00d-4237-a90a-e69419ac5216%40googlegroups.com.

[Brian Henderson]

Vincent,

thanks for your quick reply. I've been trying this with no success.

also, according to this line

https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/TcpSlaveAgentListener/index.jelly#L32

It seems like CLI_PORT is not properly being advertised, am I looking in the right place?

[Vincent Latombe]

CLI_PORT is advertised there https://github.com/jenkinsci/jenkins/commit/86bf6b7603c5c51c8ffc34fe1e78698fa9d03d3e but for JNLP you may be right (in my setup I don't override the port, only the host so I didn't notice that).

Probably an issue to file to jenkins core.

Vincent

[Brian Henderson]

sent a PR.

https://github.com/jenkinsci/jenkins/pull/2189

thanks,