Hi Mark,
In my job, my upstream job was passing downstream the following using the
predefined parameter:
BUILD_NUM=1605.132
In the downstream job I use the parameter as a build_name, as well as an
environment variable. The first issue is that when trying to set the build
name using the BUILD_NUM property, I get the following:
Set build name.
Unrecognized macro 'BUILD_NUM' in '${BUILD_NUM}'
Second issue is in a shell, when trying to use it as an environemnt variable I
get:+ echo "BUILD_NUM = $BUILD_NUM"
BUILD_NUM = $BUILD_NUM
I would think others are in my situation as well. I took a look at the source
on GitHub and it doesn't seem like the plugin is sending them as
'safeParameters' as the security notice states and no updates/releases to the
plugin have been done since Dec 2015. On the page SECURITY-170
<https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170>,
it states 'only build parameters that have been explicitly defined in a job's
configuration will be available', so the plugin needs to mark them as 'safe' to
have them passed to the downstream job as far as I can tell.
Am I reading the security notice correctly?
Thanks,
Mark B.
On Friday, May 13, 2016 at 12:16:38 PM UTC-7, Mark Waite wrote:
>
> I don't know that another JIRA issue is the solution. I found that
> passing parameters downstream works (at least for me) if the downstream job
> has a parameter named which matches the parameter being passed from the
> upstream job. Could you try the same thing in your case to see if it
> resolves it for you as well?
>
> My upstream job was passing the parameter, then my downstream job was
> reading it as an environment variable, rather than as a job parameter.
>
> Mark Waite
>
> On Fri, May 13, 2016 at 12:54 PM Mark Bretl <mark_...@hotmail.com
> <javascript:>> wrote:
>
>> Hi All,
>>
>> I have run into an issue with the Parameterized Trigger Plugin after
>> upgrading to the latest LTS build 1.651.2, where the triggered parameters
>> (using Predefined) are not being passed to the downstream job. I read the
>> security notes and found that SECURITY-170 could be affecting my issue. I
>> decided on doing the workaround of adding -D
>> hudson.model.ParametersAction.keepUndefinedParameters=true and now the
>> parameters are being passed again.
>>
>> I see that there is an issue open,
>> https://issues.jenkins-ci.org/browse/JENKINS-34814, however, it is
>> against another plugin. Should I create a new JIRA issue for the
>> parameterized trigger plugin?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-use...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/b253b369-f730-4221-a9b5-ff8d9a02c6ec%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/b253b369-f730-4221-a9b5-ff8d9a02c6ec%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/61a7524b-27d0-4609-aac8-bac9ef994626%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
