jenkins-inheritance-plugin ownership

[David Tanner]

Hello,

The jenkins-inheritance-plugin appears to be abandoned, but is required by several other plugins, like the Git plugin.  I don't want to take ownership of the project, I would like to create and merge a pull request to fix an issue in it with the Rebuild plugin.  Can Jenkins make a fork of the plugin that can then be published?

Thanks,

David Tanner

[Daniel Beck]

> On 31. Aug 2018, at 18:12, David Tanner <darth...@gmail.com> wrote:
>
> The jenkins-inheritance-plugin appears to be abandoned, but is required by several other plugins, like the Git plugin

There's only a single plugin with an optional dependency on project-inheritance, and that's promoted-builds. That, in turn, is an optional dependency of git, and a mandatory or optional dependency of a dozen or so other plugins. So no plugin actually _requires_ project-inheritance.

So this is not quite as central to the plugin system as you make it out to be. Perhaps you're just experiencing JENKINS-33843?

[David Tanner]

Hello Daniel,

Correct on both counts, it is an optional dependency that I have to install.  Since JENKINS-33843 has been open for a while, and there have been no updates to the inheritance plugin for even longer, what other option is there in this case?

Thanks,

David Tanner

[Daniel Beck]

> On 31. Aug 2018, at 19:41, David Tanner <darth...@gmail.com> wrote:
>
> Correct on both counts, it is an optional dependency that I have to install.

You don't. It's optional. That's why Git Plugin has 156,000 installs, and project-inheritance has 1832.

Comments to JENKINS-33843 describe a workaround if you already have it installed.