![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
domi
|
|
Attachments:
|
Problem-ParameterIsLost.docx |
|
Components:
|
managed-scripts, run-condition |
|
Created:
|
10/Apr/13 1:50 PM
|
|
Description:
|
The GUI is on master, the execution is on slave.
I want to use conditional step and call a manage windows batch file there with arguments.
After defining and saving, the argument is lost.
I see that during execution (the parameter is empty within the script) and I see that in configuring again the jenkins job: the argument is gone.
Please find the screenshots in the attachments.
Versions:
Jenkins: 1.501
Run Conditional Plugin: 0.10
Managed Script Plugin: 1.0.1
Thank you for handling this problem !!!
I already opened a similar problem referring to testlink plugin:
https://issues.jenkins-ci.org/browse/JENKINS-16294
in Jan/2013, but it was not assigned. Please help. Thank you.
|
|
Due Date:
|
24/Apr/13 12:00 AM
|
|
Environment:
|
Master: Microsoft Windows XP Professional 2002, SP3, 2GB RAM
Slave: Microsoft Windows 7 Enterprise 2009 SP1, 4GB RAM
|
|
Fix Versions:
|
current |
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
build
jenkins
windows
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Angela Bauer
|
|
|
|
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/groups/opt_out.
