[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible

[dnusb...@cloudbees.com (JIRA)]

Title: Message Title

Devin Nusbaum commented on JENKINS-60216   Re: Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible Bogomil Vasilev In all cases, your builds continued working, right? The problem was just that you started to see a warning telling you that the parameter types were mismatched? Or did the builds where the downstream job was a node parameter start failing? If your builds where the downstream job was using a node parameter were working before the fix, then maybe you could just switch the downstream job to have a string parameter instead (which would match the behavior from before this change would made), and if the builds started failing after the fix, then that is definitely what you should do. Otherwise, you can safely ignore the message in the build logs (maybe we could add a way to suppress the conversion messages if that is important). As far as the right syntax to use so that no conversion is needed, it looks like Node and Label Parameter Plugin does not support Pipeline syntax natively (there is no symbol like "node" or "nodeParam" or anything), and perhaps there are other bugs that make it not work correctly (see PR 14, not sure what that is about), and it has some bug that makes the explicit data binding syntax not work either (JENKINS-47571), so I'm not totally sure how to use it correctly from Pipeline. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203189.1574194043000.2986.1575904500165%40Atlassian.JIRA.