Thanks all! I've been trying to reconcile this version with what I had going in https://github.com/jenkinsci/saltstack-plugin/tree/classing. I'll keep poking at it.
At the moment, I'm attempting to discern how to get my dropdown selection to instantiate my class. So if the dropdown displays "local" the appropriate config.jelly is loaded, and I'd like the values from that page to instantiate my com.waytta.clientinterface.LocalClient class, while the main form continues to create the normal com.waytta.SaltAPIBuilder one. At the moment I everything in LocalClient is null, so I've got some fiddling to do. As far as the make things better comments: > Break up constructors into ones with fewer arguments, and do the rest with > @DataboundSetters, so fields with sensible defaults can be omitted from > pipeline script Some work has been done for this in the classing branch > - Really move parameters for specific client interfaces into their classes > (making existing fields transient) Also partially done in the classing branch - add readResolve compatibility code so existing job configs can be read > successfully I don't know what this means. Do you have an example? - @Symbol support for easier to read pipeline scripts Done in the classing branch - I'm not really happy with the $class/f:class-entry but otherwise I got > Stapler errors, will need to look into alternatives Also not sure what this means, so I'll investigate Jesse's suggestion with f:dropdownDescriptorSelector. Seriously, thanks everyone! -- 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/CAPnfjndXVQ08wrOEUL8cr2cX%2BChNJ35%2BMNk5-8RX0r1CbuZ1OA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
