[
https://issues.jenkins-ci.org/browse/JENKINS-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160669#comment-160669
]
Ross Rowe commented on JENKINS-7830:
------------------------------------
Okay, the resolving of the environment variables in the configuration fields
sounds reasonable, and it shouldn't be too difficult. And yes, my recent
change was to store the actual values into updated variable names.
I'll let you know when I've got an updated version of the plugin that includes
the change.
Cheers,
Ross
> 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
