On Sun, Aug 14, 2022 at 6:14 PM Tim Van Holder <[email protected]> wrote:
> The only thing that would be additionally useful is an automated migration > step; I wonder if there's any way I could have a button/link in the > config.jelly that would allow me to construct the new step based on the old > step's properties and have the UI take that new step into account for the > project being edited? > You may be able to readResolve them to the new type on deserialization. (Won't work for pipelines though). -- 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/CAMo7PtL8ucwpLFRCH%3DzfLZa1zrfud74d216_DtEmTxcgCugBoQ%40mail.gmail.com.
