[JIRA] Created: (JENKINS-10759) RC should try a fixed port first, and only fall back to random port if that doesn't work

RC should try a fixed port first, and only fall back to random port if that doesn't work
----------------------------------------------------------------------------------------

                 Key: JENKINS-10759
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10759
             Project: Jenkins
          Issue Type: Improvement
          Components: selenium
            Reporter: edovale
            Assignee: Kohsuke Kawaguchi


It is quite inconvenient to have the RC running on random ports specially when running it on a cloud. It would be way better to be able to tell the port before hand to be able to plan for the firewall configuration

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Richard Lavoie commented on JENKINS-10759

RC should try a fixed port first, and only fall back to random port if that doesn't work

With the latest plugin version (since 2.1), you can specify on which port the selenium node should listen for requests. Or are you taking about the high ports to make jenkins connect to childs with the remoting library (-connectTo parameter) ?

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