|
||||||||
|
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.
To get things started, yes this appears to be originating in the patch I submitted, so I'll field any fixes.
I think an ideal solution would be to simply try/catch the attempt to convert the value and if an IllegalArgumentException gets thrown back, simply use the original value instead of trying to convert it. Although this contravenes the definition of the parameter on the target job, it will broaden compatibility with any existing use cases.
@dmaslakov, I am hesitant to make this behavior optional as it better ensures the parameters behave as their defined rather than how they're passed. I would propose, instead, that the choice parameter be extended with an optional "accept anything" behavior to accommodate @mwebber's particular use case.