[
https://issues.jenkins-ci.org/browse/JENKINS-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162559#comment-162559
]
Ken Garland commented on JENKINS-13701:
---------------------------------------
I've also just tried to setup a build that uses file based parameters with "Set
environment variables through a file" and the parameters are not sent to the
job at run time.
Build > Execute shell > Command echo $temp_name
[envfile] temp_name=test
[workspace] $ /bin/sh -xe /tmp/hudson2757699259452188104.sh
+ echo
As you can see, echo has nothing afterwards.
This works on the first run.
> Parameters lost on retry
> ------------------------
>
> Key: JENKINS-13701
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13701
> Project: Jenkins
> Issue Type: Bug
> Components: naginator
> Affects Versions: current
> Environment: Jenkins 1.463, Naginator 1.6.1, Parameterized Trigger
> 2.14
> Reporter: Ken Garland
> Assignee: Nayan Hajratwala
> Labels: naginator, plugin, trigger
>
> Parameters are not passed onto newly started Naginator jobs.
> Started by Naginator
> [EnvInject] - Loading node environment variables.
> Building in workspace /root/.jenkins/jobs/test/workspace
> Checkout:workspace / /root/.jenkins/jobs/test/workspace -
> hudson.remoting.LocalChannel@2a2bfd5
> Using strategy: Default
> [workspace] $ /bin/sh -xe /tmp/hudson3453253707221002170.sh
> + python test.py --hostname
> There should be a value after "--hostname" as it is in the original build
> before failure.
--
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
