[
https://issues.jenkins-ci.org/browse/JENKINS-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161119#comment-161119
]
Lorrin Nelson commented on JENKINS-7830:
----------------------------------------
BTW, what's got me confused is that I'm upgrading from an old version of the
plug-in in which you configured both ends of the SSH tunnel (like this
http://wiki.hudson-ci.org/display/HUDSON/Sauce+OnDemand+Plugin). With the
current UI, you only input a "Sauce OnDemand Host" and "Sauce OnDemand Port".
What does that mean? Don't I need a host and port to point the browser at
(formerly "domain" and "remote port") and then a host and port that traffic
should go to on my local network (formerly "local host" and "local port"). In
the current UI, I don't get whether I'm configuring the port the browser should
hit to go into the tunnel or the port my app is listening on when the traffic
comes out.
> using environment variable for local port of ssh tunnel
> -------------------------------------------------------
>
> Key: JENKINS-7830
> URL: https://issues.jenkins-ci.org/browse/JENKINS-7830
> Project: Jenkins
> Issue Type: New Feature
> Components: sauce-ondemand
> Reporter: scytacki
> Assignee: Ross Rowe
> Fix For: current
>
>
> I use an environment variable to set the port used by the local server that I
> want to test. I do this because we want to be able to build/test the hudson
> job on multiple slave nodes at the same time. We currently have those slave
> nodes running on the same machine. If the port is hard coded then I can't
> startup multiple local servers at the same time because the port will be the
> same for each and will conflict.
> So it would be helpful if the sauce-ondemand plugin would allow using
> environment variables for the "Local Port" setting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
