Re: Incorrect rendering of job property

On Tue, Mar 8, 2016 at 5:31 AM, Mads Nielsen wrote: > Have you tried `OptionalJobProperty` in newer core versions? It covers this common use case with less boilerplate. In and of itself does not solve your issue but might make the cause clearer. -- You received this

Re: Incorrect rendering of job property

Hi Robert, Thanks for the reply...No dice on this one. I double checked the values and made two helper methods on my JobProperty: public boolean isTagFileEmpty() { return StringUtils.isBlank(tagFile); } public boolean isTaggingEmpty() { return StringUtils.isBlank(tagging); }

Re: Incorrect rendering of job property

My guess is that instance.tagFile is no longer null because the previous form posting set the value to an empty string. try checked="${not empty instance.tagFile}" or maybe it's the other way around (${instance.tagFile not empty}), those jexl expressions confuse me sometimes ;) /B On Tue, Mar

Incorrect rendering of job property

Hi Guyes, I have a problem. What im trying to do is to have Jenkins render a radio-button group with mutually exclusive options in a Job property. This work fine when the job is getting configured. But when i reload the page...i get this: ​Even though i have not selected the File from