[
https://issues.jenkins-ci.org/browse/JENKINS-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160635#comment-160635
]
Lorrin Nelson commented on JENKINS-7830:
----------------------------------------
Hey Ross, thanks for the quick turn-around! I'm a little confused by your
response though. My (and I think the original poster's) intent was to be able
to use environment variables in the existing Jenkins Tunnel Configuration
fields. E.g. instead of entering a specific number, I want to put $MY_VARIABLE
as the Local Port. $MY_VARIABLE will be set by some other process or plug-in
and Sauce OnDemand will consume it at runtime.
If I'm following you right, your change was to publish the values (which still
must be directly specified or defaulted) into new variables?
Cheers!
-Lorrin
> 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
