On Mon, Apr 18, 2022 at 3:16 PM 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> Potentially doable via readResolve as well.
>
>
Unfortunately you cannot do this sort of thing via `readResolve` so far as
I know.
Ideally there would be some API which you could call
> On 18. Apr 2022, at 10:38, Tim Van Holder wrote:
>
> 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?
Potentially doable via readResolve as well.
--
You received this message because
On Mon, Apr 18, 2022 at 4:38 AM Tim Van Holder
wrote:
> 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?
>
It is possible with an `@Initializer`.
I'd have to keep them around for pipeline use
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
On Tue, Apr 12, 2022 at 1:40 PM Tim Van Holder
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
I did consider that, but I'm currently using SimpleBuildStep to provide the
steps to both freestyle and pipeline contexts.
If I make that one step, that would make the experience in pipelines rather
messy, with lots of properties that would only apply for a specific
combination of other
On Mon, Apr 11, 2022 at 11:53 PM Tim Van Holder
wrote:
> I maintain a plugin (dotnet-sdk) that mostly provides a global tool and
> associated wrapper.
> But it also has a bunch (currently 11) convenience steps that can be used
> (instead of the wrapper plus bat/pwsh/...).
> I got a ticket saying
Hi,
I maintain a plugin (dotnet-sdk) that mostly provides a global tool and
associated wrapper.
But it also has a bunch (currently 11) convenience steps that can be used
(instead of the wrapper plus bat/pwsh/...).
I got a ticket saying that this caused a bit of a clutter for freestyle
jobs,