[JIRA] [core] (JENKINS-23937) No user interface for "-tcp PORT" slave jar option

[dan...@beckweb.net (JIRA)]

Daniel Beck
 commented on  JENKINS-23937


No user interface for "-tcp PORT" slave jar option















The problem is that an undocumented option seems worse than a documented option nobody needs.

It's also difficult to tell whether it's actually unused by everyone – even if not used in Jenkins out of the box, someone may have a custom ComputerLauncher that breaks when removing that option. Maybe for "run a command on the master"?

Or can you show it must be unused, because it's actually broken in some way?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23937) No user interface for "-tcp PORT" slave jar option

[cr...@2ndquadrant.com (JIRA)]

Craig Ringer
 created  JENKINS-23937


No user interface for "-tcp PORT" slave jar option















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


23/Jul/14 6:25 AM



Description:


While debugging JENKINS-23917 I noticed that the slave option:


-tcp FILE   : instead of talking to the master via
   stdin/stdout, listens to a random local
   port, write that port number to the given
   file, then wait for the master to connect to
   that port.


doesn't seem to have any UI in Jenkins node configuration to actually use it, at least for ssh or jnlp slaves. You can specify it as a command line suffix, but there's no way to tell Jenkins that it should make a connection to the agent.

Minor, as it's not super useful for an ssh slave, and for a jnlp slave it's already using JNLP by connecting to the Jenkins master. I only noticed it while debugging.

Perhaps it's best to just remove it from the help output or note that it's for future use?




Environment:


Jenkins ver. 1.574-SNAPSHOT




Project:


Jenkins



Priority:


Trivial



Reporter:


Craig Ringer

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.