[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Artem Bityutskiy edited a comment on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters I see the same issue. Jenkins ver. 1.625.3, Parameterized Trigger plugin 2.30. This kind of stuff happens very often with Jenkins and plugins. Really frustrating. Any workaround? Anyway, this turns out to be the way Jenkins community fixed the security issue:https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11Just run Jenkins with this Java option and you'll have the old behavior back:-Dhudson.model.ParametersAction.keepUndefinedParameters=trueIn my setup I basically edited /etc/sysconfig/jenkins:JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true"HTH Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Artem Bityutskiy edited a comment on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters I see the same issue. Jenkins ver. 1.625.3, Parameterized Trigger plugin 2.30.This kind of stuff happens very often with Jenkins and plugins. Really frustrating. Any workaround? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Artem Bityutskiy commented on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters I see the same issue. Jenkins ver. 1.625.3, Parameterized Trigger plugin 2.30. This kind of stuff happens very often with Jenkins and plugins. Really frustrating. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Artem Bityutskiy updated an issue Jenkins / JENKINS-29031 Current Build Parameters doesn't pass custom job parameters Change By: Artem Bityutskiy Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Victor L commented on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters Me too. Had to downgrade from 1.651.2 back to 1.642.4. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title B Hicks commented on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters My Jenkins server is also affected by this bug. Parameterized projects are not passing those parameters to chained projects even when "Current build parameters" are included for the target project. This is infuriating as this bug has effectively broken most of my build jobs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Regina Obe commented on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters I just ended up downgrading back to old jenkins and that fixed my issue. I won't upgrade until this issue is fixed or there is an easy work around. Only work aorund I found was to make my build parameters matrix parameters, but that requires changing a good chunk of my matrix jobs and suboptimal. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Regina Obe commented on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters I have the same issue after upgrading from 1.595 and related plugins. I tried downgrading Parameterized trigger plugin to 2.25 (which was one that used to work), but that did not fix the issue. Is there some other plugin I need to downgrade or should I downgrade my Jenkins? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Andrew Hammett commented on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters it appears that only server-side environment variables are being parsed as parameters and all other values are being passed as literals. As an example if I were set the following "predefined variables" for any given job ``` FOO=$BAR GIT_COMMIT=$GIT_COMMIT ``` The $GIT_COMMIT value would be evaluated with $FOO being treated as literal $BAR. I have tried: ``` foo=baz export FOO=foo ``` using each of the above separately ultimately results in the same. the job being triggered will receive FOO=$BAR where $BAR is not evaluated (and does not show baz or foo). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title Kazuyuki Ohgushi commented on JENKINS-29031 Re: Current Build Parameters doesn't pass custom job parameters I met the same problem in Jenkins ver. 1.621 and Parameterized Trigger plugin 2.27. Environment variables like $BUILD_NUMBER are passed to downstream jobs, but predefined parameters with current job parameters are not. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title C. S. created an issue Jenkins / JENKINS-29031 Current Build Parameters doesn't pass custom job parameters Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 23/Jun/15 8:46 AM Priority: Minor Reporter: C. S. I have recognized that using Current Build Parameters when triggering another job doesn't pass custom job parameters. Job A and B have both a parameter called "DAILY_BUILD". Using Current Build Parameters doesn't pass DAILY_BUILD to job B. Add Comment
