On Friday, February 20, 2015 at 2:37:21 AM UTC-5, [email protected] wrote: > > 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) >
You guessed right. For certain kinds of parameters, there may be a more natural Groovy object that the value could be set to. The Jenkins API for ParameterValue does now (1.568+) define getValue. Changing the way parameters are bound in workflows now would be a compatibility break, unless you opted in to the change in behavior somehow, so TBD. File an RFE for it if you think it is important. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/da4255f3-ae88-43a0-91f2-49c9ad0b8e70%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
