This is a comparable issue indeed, even this applies to updateByXml. not configure(json) https://github.com/jenkinsci/jenkins/pull/2736 is a promising approach, but is discovering attributes via reflection, while configuration-as-code is looking at ui-bound parameters. In many case they are the same but not always the case. Anyway this gives me some inspiration to propose a fix.
2017-11-13 21:45 GMT+01:00 Daniel Beck <m...@beckweb.net>: > > > On 13. Nov 2017, at 20:26, Jesse Glick <jgl...@cloudbees.com> wrote: > > > >> > >> if I UNCHECK the optional property, no "authentication" value > >> is posted to JSON form, and I don't get SMTPAuthentication reset to > null in > >> my descriptor. > > > > Unfortunately your `configure` override must start by setting any > > optional struct fields to null: > > Is this just JENKINS-21017 again, or something else? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/230C492B-23E2-4816-BB0A-5647E749AB15%40beckweb.net. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznZpTa%2B7_uC8NvoTd5fBW-33rMWpsaKkG8%2BupVVB5P-%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
