On Sun, Aug 14, 2022 at 12:14 PM Tim Van Holder <[email protected]> wrote:
> there seems to be no checking that such a symbol is valid/usable, neither > at build time nor at run time. […] It would certainly be useful to get a > diagnostic for that at maintenance/build time Might be possible at runtime. I'm using <f:dropdownDescriptorSelector> for the nested describables which > mostly works nicely. However, this does not surface any help files for the > selected describable in the UI. Is that a bug Try updating to latest core. So my only option would seem to be to essentially create a new set of Steps > just so they could have descriptors marking themselves as advanced > Yes. that would involve the symbols being associated with those new classes; > would that break anything? > No, symbols must only be unique per domain. The old class would remain a Builder > Just make it not be a `SimpleBuildStep`. is all this just a consequence of the steps in question getting run via a > meta-step? > Yes. -- 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/CANfRfr1uZ1sOE3242hwdvnt534mpXCO6P48NAtaVBC4LUpka3Q%40mail.gmail.com.
