Deprecate jenkins-slave launcher in favor of one using -jnlpUrl

[jglick]

The normal way to launch inbound agents, as advertised on the agent page, is

java -jar agent.jar -jnlpUrl http://jenkins/computer/myagent/slave-agent.jnlp -secret XXX

This goes through hudson.remoting.Launcher, which downloads the result of SlaveComputer/slave-agent.jnlp.jelly. That exposes JNLPLauncher.tunnel and .workDirSettings, does some other preparation, and finally delegates to the lower-level hudson.remoting.jnlp.Main.

For some reason I cannot follow, jenkins-slave in this image runs hudson.remoting.jnlp.Main directly, ignoring any tunnel and/or workDirSettings configured in the launcher.

Not sure if an existing entrypoint be deprecated. Perhaps this whole image should be deprecated in favor of one using the more convenient launcher class.

[jglick]

See also kubernetes plugin setup.

[jglick]

On the other hand this would not be compatible with direct connection mode (-direct, -instanceIdentity, -protocols) as in jenkinsci/docker-inbound-agent#118, the whole point of which is to avoid making an HTTP connection.

[jglick]

No longer intending to do this.