Re: Splitting a plugin into a legacy and supported part

> Am 13.10.2023 um 15:02 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Fri, Oct 13, 2023 at 2:38 AM Ullrich Hafner > wrote: >> there might be still some users that use the old and deprecated steps > > Like, Pipeline steps? So you cannot confidently

Re: Splitting a plugin into a legacy and supported part

On Fri, Oct 13, 2023 at 2:38 AM Ullrich Hafner wrote: > there might be still some users that use the old and deprecated steps > Like, Pipeline steps? So you cannot confidently delete this code without potentially breaking user workflows? > Move the old code to a new plugin with new plugin id.

Re: Splitting a plugin into a legacy and supported part

On Fri, Oct 13, 2023 at 8:38 AM Ullrich Hafner wrote: > Or is there even anotheroption that I do not see? > Depending on the scope of the problem, deprecation and finally removal of the obsolete stuff you want to remove. Use usage-in-plugins to identify callers and consider providing

Splitting a plugin into a legacy and supported part

Hi, I want to retire a lot of old and legacy code in the code-coverage-api plugin in order to simplify the development experience (e.g., there are duplicate classes and jelly views). It is difficult for new contributors to start development when they do not know which classes and views are