Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page is a work in progress – the plugin info plugin has not yet been updated, so no message appears on labeled plugin pages!

We're looking for new maintainers of existing plugins!

You want to help and are looking for a plugin to maintain

Check out this list of plugins up for adoption here. If you see a plugin you like, visit its wiki page as it may contain additional information about the adoption request.

You know which plugin you want to help with

Once you've chosen a plugin, review the documentation on plugin maintainership in the Jenkins project. This is especially important if you're not currently a plugin developer.

As a new maintainer of a new plugin, you'll inherit its existing users, so be careful with breaking changes. We value data compatibility highly, so any new releases should remain compatible with previous data and upgrade smoothly. If you need help with this, don't hesitate to ask other Jenkins developers for help. And if all else fails, you can mark a new version as being incompatible with older releases to warn users before they update.

Request commit access

Email the Jenkins Developers mailing list and request to be made a maintainer (which usually means commit access to the plugin repository and being made default assignee for newly reported issues in JIRA). It's possible that handling your request takes a few days and may include an attempt to exist previous maintainers, so be patient.

How to mark a plugin for adoption

First, make sure the plugin is not being actively maintained. Even in actively maintained plugins, there may be periods of lower developer activity. Don't misinterpret failures to respond to questions or requests as the plugin being unmaintained!

To mark a plugin for adoption, add the adopt-this-plugin label to the plugin's wiki page. This will cause the note to appear below the plugin info box.

If you want to customize the message, use the adopt-message parameter to the jenkins-plugin-info macro, e.g. like this:

{jenkins-plugin-info:myplugin|adopt-message=The maintainer is looking for a co-maintainer.}

This message will replace the default Want to help improve this plugin? text in the note.

I'm a plugin maintainer and my plugin shows as up for adoption, why?

Plugin pages are labeled adopt-this-plugin manually, so it's likely a mistaken assumption that your plugin is unmaintained. If you remove the label from its wiki page, it'll disappear from the list again.

  • No labels