Daniel offered a similar suggestion off-list. I'll have a look once I get a release out with what I have now.
One question though - what would the migration path be like? Can a plugin include code that will update a freestyle project that uses the DotNetFoo builder to use the DotNet builder with a Foo argument instead? I would assume I'd normally have read-only access to the freestyle jobs. I suppose I could just keep both around, with isApplicable() for the old ones returning false (so that existing uses remain valid, but only the new builder could be used for new steps), but an automatic upgrade would be nice too. I'd have to keep them around for pipeline use anyway; is there anything in Jenkins that will report warnings for use of deprecated steps in a pipeline job? There's no isApplicable() there to keep them from being written in scripts, so if I can at least have the build report that the new steps should be used instead, that's something. I wouldn't want to keep the old builders around in perpetuity (even if they can become simple wrappers around the new one). On Fri, 15 Apr 2022 at 21:25, 'Jesse Glick' via Jenkins Developers < [email protected]> wrote: > On Tue, Apr 12, 2022 at 1:40 PM Tim Van Holder <[email protected]> > wrote: > >> a relatively simple way to have a build step for freestyle that would >> essentially then have a dropdown for the 11 "real" steps which then shows >> their configuration when selected >> > > This is straightforward. (`ui-samples-plugin` may be instructive.) Just an > abstract `Describable` supertype for the real things, and the `config.xml` > for the `Builder` can have a `f:dropdownDescriptorSelector` and maybe > nothing else. Each real thing has its own `config.jelly`. If you also add > `@Symbol`’s, then for Pipeline you would get syntax like > > dotnet tool: makeAssembly(assemblySpecificOption: true), genericOption: > 'whatever' > > -- > 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/CANfRfr3eG-v5vNV4ScKYLPHRSCgCheLjGJsQ9H7_JVCbmTx6Xw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3eG-v5vNV4ScKYLPHRSCgCheLjGJsQ9H7_JVCbmTx6Xw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAKMi--D%3DfSYQLej3Pqx7autnAm3izuGbhHQ4sNkN9suW09HwYQ%40mail.gmail.com.
