On Friday, February 20, 2015 at 8:11:38 AM UTC+1, Vincent Latombe wrote: > > No, it is how the groovy truth is defined. See > http://docs.codehaus.org/display/GROOVY/Groovy+Truth > Non-empty strings are coerced to true, even if the value is "false". >
Yes, I agree with that, there is no Groovy bug here. 2015-02-20 6:11 GMT+01:00 Jos Backus <j...@catnook.com <javascript:>>: > >> But isn't that a bug? Why doesn't the surrounding code cast the parameter >> to a Boolean value, as certainly I would expect? >> > I'm tempted to agree with Jos too, why is the variable created by a "Boolean Build Parameter" (from the top of the job configuration page) not a boolean variable in the first place? I guess is has something to do with compatibility with non-workflow jobs, which access the parameter as an environment variable (instead of a groovy variable), but you got the point. Sébastien >> -- >> 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/a5c46e5e-6dec-4736-ba5d-4653f2da7695%40googlegroups.com >> . >> 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/4534cee4-f803-47d7-ba01-fd7ea4a23fb5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
