dmaslakov commented on Bug JENKINS-22125

Change log of Parameterized Trigger Plugin describes the change "Now attempts to convert parameter strings to the type defined in the project" which is likely the reason of described error.

In any case I also had have the same error after plug-in upgrade. More details:

  • job A has parameter P of type 'choice' with number of predefined values a, b, c (Job A is the main job with build steps.)
  • job B extends the values of parameter P, precisely, it has parameter P as a choice of values e, f, g (Job B is a wrapper job, it mangles parameters and calls job A for the real work.)
  • in version 2.22 all worked fine as parameters was not converted and under the hood Jenkins does not care about parameter types, they are just strings
  • in version 2.23 the converting of parameter values fails

Of course, here is a work around for described case: a) convert parameter P of main job A to be a string, b) create wrapper job C with parameter P as a choice of a, b, c, and call job A. But this work around assumes that conversion of choice parameter into string parameter will not fail.

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to