Skip to end of metadata
Go to start of metadata

We're looking for new maintainers of existing plugins!

A plugin I'm (planning on) using shows up as looking for a maintainer. Does that mean I shouldn't use it?

No. Jenkins is designed with backward compatibility in mind, so it's rare that a plugin stops working. And even then there's often someone who can fix the bug and release a new version even if they wouldn't be considered a maintainer of the plugin. So if you're happy with what a plugin is offering, there's no reason not to use it just because it's up for adoption.

I want to help! How can I find a plugin to maintain?

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

I know which plugin I want to help with, what should I do now?

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).
To that purpose, it's expected to try and reach out to existing maintainer(s) using a best effort. So, the typical way to do that is to put her/his/their email addresses in CC (hint: Git commits should have this information).

We typically wait for about 2 weeks in normal work periods before proceeding, so please be patient. Hence, if you can prove the existing maintainer already agrees and you explicitly asked about taking over (e.g. in a PR discussion), the process can be fast-looped.

IMPORTANT: To speed up and ease the process, please provide the two following things:

Once granted access, you can file a PR (with your Jenkins infrastructure account id) against https://github.com/jenkins-infra/repository-permissions-updater to be able to deploy snapshots and releases for your plugin. You're generally expected to start slowly, by filing PRs, and not commit directly. Even more for plugins with a big number of installations for obvious reasons.

How can I 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.

IMPORTANT: please use the Comment: textfield of Confluence page edition to explain why you're marking that plugin as up for adoption. Ideally, link to a thread on the mailing-lists, GitHub or somewhere else with a message from the current maintainer(s) confirming that the plugin is indeed not maintained anymore.

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?

This status is based on the adopt-this-plugin label on the plugin wiki page. 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.

Which plugins are currently up for adoption?

The following is a list of plugin pages with the adopt-this-plugin label.

  • Page:
    Accelerated Build Now Plugin — The Jenkins Accelerated Build Now Plugin allows Jenkins users to launch a project's build right away, even if the queue is long (moving it to the top of the queue) and even if no executor is available (killing and rescheduling builds not launched by "humans")
  • Page:
    AccuRev Plugin — This plugin allows you to use AccuRev as a SCM.
  • Page:
    Amazon EC2 Plugin — Allow Jenkins to start slaves on EC2 or Eucalyptus on demand, and kill them as they get unused.
  • Page:
    Amazon ECR — This plugin offers integration with Amazon EC2 Container Registry (ECR) as a DockerRegistryToken source to convert Amazon Credentials into a Docker CLI Authentication Token.
  • Page:
    ArtifactDeployer Plugin — This plugin makes it possible to copy artifacts to remote locations.
  • Page:
    AWS Cloudformation Plugin

    A plugin that allows for the creation of cloud formation stacks before running the build and the deletion of them after the build is completed.

  • Page:
    AWS SQS Plugin — Jenkins plugin that triggers builds on events that are published via Amazon Simple Queue Service (SQS)
  • Page:
    Backup Plugin — Backup plugin allows archiving and restoring your Jenkins (and Hudson) home directory.
  • Page:
    BruceSchneier Plugin

    Displays a picture of Bruce Schneier (instead of Jenkins the butler) and a random Bruce Schneier fact on each build page.

  • Page:
    Build Name Setter Plugin — This plugin sets the display name of a build to something other than #1, #2, #3, ...
  • Page:
    BuildResultTrigger Plugin — BuildResultTrigger makes it possible to monitor the build results of other jobs.
  • Page:
    Collapsing Console Sections Plugin — This plugin allows the creation of sections in build consoles.
  • Page:
    Configuration Slicing Plugin — Perform mass configuration of select project properties, including email, timer, discard old builds, and Maven configuration.
  • Page:
    Console Column Plugin — Provide a fast-path console link available for views.
  • Page:
    Console Tail Plugin

    This plugin adds a floating box to all projects when the last build failed. The floating box is only shown if the last build failed.

  • Page:
    Copy To Slave Plugin — This plugin allows to copy a set of files, from a location somewhere on the master node, to jobs' workspaces. It also allows to copy files back from the workspaces of jobs located on a slave node to their workspaces on the master one.
  • Page:
    CPPNCSS Plugin — This plugin allows you to use CppNCSS build reporting tool.
  • Page:
    Cpptest Plugin

    This plugin allows you publish Parasoft C++test test results.

    This plugin makes it possible to import Parasoft C++test reports from each build into Hudson so they are displayed with a trend graph and details about which tests that failed.

  • Page:
    CVS Plugin — This bundled plugin integrates Jenkins with CVS version control system.
  • Page:
    Cygwin Process Killer Plugin — Plugin implements proper termination of Cygwin processes in Jenkins jobs
  • Page:
    Dependency Graph View Plugin — Shows a dependency graph of the projects using graphviz. Requires a graphviz installation on the server.
  • Page:
    Deployed on Column Plugin — This plugin provides a column that acts as a container for build actions that record deployment of build artifacts to remote servers, such as deployment of web applications to servers, etc. The plugin also provides an extension point for other plugins to contribute their build actions.
  • Page:
    Downstream buildview plugin — This plugin allows you to view the full status all the downstream builds so that we can graphically see that everything for this build has been completed successfully.
  • Page:
    DTKit Plugin — This plugin makes it possible to convert outputs from the metric tools execution into unified outputs.
  • Page:
    Dynamic Search View Plugin — Adds a new list view, which allows to dynamically specify additional filters.
  • Page:
    Email-ext plugin — This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says.
  • Page:
  • Page:
    EnvInject Plugin — This plugin makes it possible to have an isolated environment for your jobs.
  • Page:
    Extension Filter Plugin — This plugin allows to filter features available on a Jenkins instance by disabling some Extensions/Descriptors.
  • Page:
    Firefox Add-on Build Monitor — Monitor Jenkins builds and display the status on Firefox status bar.
  • Page:
    FSTrigger Plugin — FSTrigger provides polling mechanisms to monitor a file system and trigger a build if a file or a set of files have changed.
  • Page:
    GitHub pull request builder plugin — This plugin builds pull requests in github and report results.
  • Page:
    GitLab Auth — This plugin provides authentication for GitLab users.
  • Page:
    Gnat Plugin — This plugin makes it possible to integrate Gnat features for Ada languages in Jenkins.
  • Page:
    Groovy Events Listener Plugin — A Jenkins plugin, which executes groovy code when an event occurs.
  • Page:
    Harvest Plugin — This plugin allows you to use CA Harvest as a SCM.
  • Page:
    Ironmq Notifier — This plugin uses the IronMQ messaging service to send status updates of build information into an enterprise level cloud based message queue.
  • Page:
    IvyTrigger Plugin — IvyTrigger provides polling mechanisms to poll an Ivy file and triggers a build if an Ivy dependency version has changed.
  • Page:
    JavaNCSS Plugin — This plugin allows you to use JavaNCSS build reporting tool.
  • Page:
    jQuery UI Plugin — This plugin allows you to use jQuery UI on each view descriptions.
  • Page:
    JUnit Attachments Plugin — This plugin can archive certain files (attachments) together with your JUnit results.
  • Page:
    Label Verifier Plugin — This plugin allows system administrator to programmatically verify the label assignment correctness on slaves.
  • Page:
    Locks and Latches plugin — This plugin allows you to control the parallel execution of jobs.
  • Page:
    Mask Passwords Plugin — This plugin allows masking passwords that may appear in the console
  • Page:
    Nested View Plugin — View type to allow grouping job views into multiple levels instead of one big list of tabs.
  • Page:
    Node Stalker Plugin — This plugin lets you configure jobs to run on the same node, and if desired the same workspace, as another job.
  • Page:
    Pathignore Plugin — This plugin allows SCM-triggered jobs to ignore build requests if only certain paths have changed, or to build if and only if certain paths are changed.
  • Page:
    PerfPublisher Plugin — This plugin generates global and trend reports for tests results analysis. Based on an open XML tests results format, the plugin parses the generated files and publish statistics, reports and analysis on the current health of the project.
  • Page:
  • Page:
  • Page:
    Poll Mailbox Trigger Plugin — A Jenkins plugin, to poll an email inbox, and trigger jobs based on new emails.
  • Page:
    Port Allocator Plugin — Assigns unique TCP port addresses to jobs so that jobs executed concurrently won't collide with each other. Also performs clean ups to kill off daemons that are forked by jobs.
  • Page:
    Release Plugin — This plugin adds the ability to wrap your job with pre- and post- build steps which are only executed when a manual release build is triggered.
  • Page:
    Remote Terminal Access Plugin — This plugin enables users to open an interactive terminal session against on-going builds on Jenkins.
  • Page:
    Repo Plugin — This plugin adds Repo as an SCM provider in Jenkins.
  • Page:
    Ruby Runtime Plugin — Provides the Ruby runtime and bindings required to implement plugins in Ruby.
  • Page:
    SCons Plugin — This plugin allows Hudson to invoke SCons build script as the main build step.
  • Page:
    SCP plugin — This plugin uploads build artifacts to repository sites using SCP (SSH) protocol.
  • Page:
    ScriptTrigger Plugin — ScriptTrigger makes it possible to monitor an environment with a script.
  • Page:
    SharedObjects Plugin — This plugin makes it possible to share objects (script file, source file, tool installation, ...) from an environment in Jenkins and manage dynamically these objects through environment variables with the EnvInject Plugin during the job build.
  • Page:
    Slack Plugin — This plugin allows to post build notifications to a Slack channel.
  • Page:
    Subversion Plugin — This plugin adds the Subversion support (via SVNKit) to Jenkins.
  • Page:
    Swarm Plugin — This plugin enables slaves to auto-discover nearby Jenkins master and join it automatically, thereby forming an ad-hoc cluster.
  • Page:
    Tattletale Plugin

    This plugin generates Tattletale reports, mostly useful for jar file analysis.

  • Page:
    Tcl Plugin — Plugin provides Tcl buildstep
  • Page:
    TestLink Plugin — This plug-in integrates Jenkins and TestLink and generates reports on automated test execution. With this plug-in you can manage your tests in TestLink, schedule and control in Jenkins, and execute using your favorite test execution tool (TestPartner, Selenium, TestNG, Perl modules, PHPUnit, among others).
  • Page:
    testng-plugin — This plugin allows you to publish TestNG results generated using org.testng.reporters.XMLReporter.
  • Page:
    Testopia Plugin

    This plug-in integrates Jenkins with Testopia and generates reports on automated test execution. With this plug-in you can manage your tests in Testopia, schedule and control in Jenkins, and execute using your favorite test execution tool (TestPartner, Selenium, TestNG, Perl modules, prove, PHPUnit, among others).

  • Page:
    thinBackup — This plugin simply backs up the global and job specific configurations (not the archive or the workspace).
  • Page:
    Throttle Concurrent Builds Plugin — This plugin allows for throttling the number of concurrent builds of a project running per node or globally.
  • Page:
    Vault Plugin — This plugin integrates SourceGear Vault/Fortress™ version control with Jenkins.

    Currently the plugin supports polling SCM for changes, triggering build if there is changes and keeping the changelog.

    This is an unofficial plugin - neither the plugin or the developer are affiliated with SourceGear.

  • Page:
    Version Number Plugin — This plugin creates a new version number and stores it in the environment variable whose name you specify in the configuration.
  • Page:
    VMware plugin — This plugin allows you to start a VMware Virtual Machine before a build and stop it again after the build completes.
  • Page:
    vSphere Cloud Plugin — Add VMware vSphere support to Jenkins by making available multiple vSphere Build Steps and supporting the use of Virtual Machines as slaves.
  • Page:
    WIX Toolset Plugin — With WIX Toolset Plugin you are able to build MSI packages from Windows Installer XML (WiX) files with Jenkins.
  • Page:
    XTrigger Plugin — The XTrigger plugin makes it possible to monitor different environments (filesystem, jobs result, url response, binary repository and so on) and triggers a build if there is at least one change between two checks.
  • Page:
    ZenTimestamp Plugin — This plugin export a BUILD_TIMESTAMP variable.

  • No labels