Thanks Jesse, the solution was indeed to implement a custom RootElementConfigurator in the plugin. (And then to do the translation between the desired CasC config model and the traditional Web form config model in the describe() method.)
Chris > On 11 Feb 2020, at 16:54, Jesse Glick <[email protected]> wrote: > > The `structs` API defines a `CustomDescribableModel` for this sort of > thing, used for example by Pipeline. However `configuration-as-code` > has its own incompatible model. I think you can implement either > `RootElementConfigurator` or `Configurable`. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0_EmQR26s7frpwRd3dPL6x0y9uA4Ch82_P3mcwuZ%2BD2A%40mail.gmail.com. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/230F4958-DF83-4C51-83DF-A5A380DA356D%40chriskilding.com.
