So last ticket is now closed.
On Sun, Apr 10, 2022 at 1:16 PM Gavin Mogan wrote:
>
> Looks like its mostly waiting for security
> https://issues.jenkins.io/browse/HOSTING-1160
>
> On Sun, Apr 10, 2022 at 12:40 PM Alex Earl wrote:
> >
> > Anything I can do to help get that one over the finish
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
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 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
> 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
