![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
sauce-ondemand-plugin |
|
Created:
|
28/Jan/15 11:23 AM
|
|
Description:
|
I have noticed that inside a job, when the Sauce OnDemand Support is selected, under "Sauce Connect Advanced Options" on line "Sauce Connect Options" user can define only one environment variable to be used at a time. For example if I would want to give these options:
--pidfile ${WORKSPACE}/sauce.pid -P ${PORT_POOL} -i ${JOB_NAME} -l ${WORKSPACE}/sauce.log
this won't work but starting the sauce connect will fail e.g.:
Launching Sauce Connect on...
- Error opening ${WORKSPACE}/sauce.log
If I define only one parameter the build will work. As a user I would want to be able to define as many of the parameters as possible as environment variables to reduce the need for hard-coding but offering job-specific flexibility.
|
|
Environment:
|
Sauce OnDemand Plugin 1.114
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Pasi Romo
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
