Hosting Plugins

Skip to end of metadata
Go to start of metadata

We encourage plugin developers to host the plugins in the Jenkins community repositories on Github.
This makes it easier for the community to help you more easily, as well as to have the community benefit from the plugin. In this way, even when you move on to something else, the community can find someone else to pick up the work.
You can take a quick look at how we work for more information.



In order to host a plugin in the Jenkins plugin Update Centre, you must:

  • Give your plugin a sensible ID which does not include jenkins or plugin
    • e.g. IDs like "jenkins-snapchat-notification-plugin" are redundant (we know it's a Jenkins plugin!); call it simply "snapchat-notification"
    • Similarly, "notification-plugin-for-snapchat" is redundant and overly-verbose; again just use "snapchat-notification"
      • This is the <artifactId> tag in pom.xml if you're using Maven
      • This is the shortName in build.gradle if you're using Gradle
      • This is the name in the .pluginspec file if you're using Ruby
  • Upload your plugin code to a repository on GitHub
  • Specify an open source license for your code (most plugins use MIT)
    • The Jenkins project does not host closed-source plugins
    • You should specify the license in the plugin metadata (e.g. pom.xml), but ideally also in a LICENSE file in the root of your repository
  • Have a account
    • This gives you access to upload your plugin, document your plugin on this wiki, and track issues in JIRA

Request hosting

Having completed the prerequisites above, join the developers' mailing list and send a message to tell us:

  • The URL to your finished plugin repository on GitHub
  • The name the repository should have (if it doesn't already have a clear name), e.g. "snapchat-notification-plugin"
    • This is because people often develop their plugin as "my-awesome-snapchat-jenkins-notifier", but we always add the "-plugin" suffix to the repo, and remove redundant stuff like "jenkins" when forking into the Jenkins GitHub organisation
  • Your personal GitHub username, if different from the username in the repo URL (GitHub organisation IDs are not supported)
  • Your username, so we can make you the default assignee for the JIRA issue tracker component for your plugin
  • A description of what the plugin does, and what makes it different from other similar plugins

You'll get commit access to the repository under

Once you have a Jenkins repository, you can start making the following preparations for your first release.

Importing source code

In some cases you may get an empty repository, rather than a fork, in which case you can import your source code:

$ cd path/to/yourplugin
$ git init
$ git add pom.xml src
$ git commit -m "initial import of my plugin"
$ git remote add origin
$ git push origin master

We also recommend you look around some other plugin's POM file (such as this) to trim off the redundant things.

For example, usually the <groupId> is removed (groupId for the plugin, not the one in the <parent> section), to use the default which is org.jenkins-ci.plugins. <repositories> and <pluginRepositories> can be removed as well. If you need help, contact the dev list.

Declare your repository in your POM

The location of your repository must be declared in the POM for plugins hosted in Github, by adding the following fragment:


Creating a Wiki page

Each plugin must have its own page on this wiki, as a child of the Plugins page.

This serves as documentation, links to the source code and issue tracker, and makes it easier for people to find your plugin via search engines.

  1. Visit the Plugins page, hover over the "Add" menu at the top right, and choose "Page".
  2. If you're asked to log in, you should use your account details
  3. Enter a page name, with each word capitalised, ending with "Plugin", e.g. "Snapchat Notification Plugin"
  4. Add a plugin "infobox" with your plugin's ID, e.g.:
  5. Add an "excerpt" below the infobox. This is a very brief description of your plugin, which will be shown to users in the Jenkins plugin manager:
    {excerpt}Allows users to send build notifications via [Snapchat|]{excerpt}
  6. Give your wiki page a label like "plugin-scm" or "plugin-misc" (click Labels at the bottom of the wiki Edit page and start typing "plugin-" to see all the possible labels).
    This will ensure the page shows up as a link in the appropriate section of Plugins.
  7. Fill out the CAPTCHA and press Save

These are the bare minimum requirements for a plugin page. This page will be linked from the Plugins page as well as directly from the Jenkins plugin manager.

Once you have made your first release, you should add changelog information to the page, and document what the plugin does, and how it is configured.

Please check out some good examples of how you should lay out your page:

If you wish, you can also manage your documentation in your GitHub repo, so long as there's a clear link from your plugin's wiki page.
See, for example, the Job DSL Plugin.

Adding your Wiki page to your repo

Now that you have a wiki page, its URL must be listed in your pom.xml like this:


If you're building your plugin with Gradle, you must set the URL in your build.gradle like so:

jenkinsPlugin {
  url = ''

Or if you have a plugin written in Ruby, you must edit your .pluginspec file like so: do |plugin|
  plugin.url = ''

This ensures that the update centre will list your plugin correctly. If this is missing, or does not point to your Jenkins wiki page, your plugin will not be included in the update centre.

Adding Maintainer Information

In your POM, make sure to include developer information, such as:

      <name>Developer Guy</name>

The ID is your account. The name is a human readable display name. This ensures that the update center and related tools are able to properly display the maintainer for your plugin.
It's highly advisable to include an email address so that people can contact you (this will be shown in the plugin infobox on the wiki), but it's optional. If pull requests go unmerged for a long time, and there's no way of contacting you, the maintainer, others will be encouraged to take over maintainership.

Continuous integration builds on DEV@cloud

To have your plugin built on, you do not need to do anything---all Jenkins plugins are automatically built as Maven jobs (clean install -e). All plugin CI broken build results will be mailed to any configured developers in the POM, plus culprits.

Ruby and Gradle plugins are also supported, but you should wave on the developers mailing list to have someone with the proper access right update the job for you.

Releasing to

The easiest way to publish a plugin is to run the maven release plugin with your account:

$ mvn release:prepare release:perform -Dusername=... -Dpassword=...

If you are using GitHub, make sure that the "origin" remote is pointed to your actual plugin repository.

This will perform all the usual Maven release activity, and it will also post the plugin to the download section. If you run with the -B option, Maven will automatically use all the default values without prompting.

Do not split that Maven command into two separate Maven invocations (i. e. mvn release:prepare followed by mvn release:perform): It won't work as you expect and will mess up your release. Always execute the two Maven goals together, in one command.
If you get back an 401: Unauthorized or if you encounter any other problem releasing your plugin while providing username and password as environment variable, try to pass username and password for authentication by modifying your settings.xml as described below.

However if your plugin is hosted on GitHub and you have different username and/or password for GitHub and use of the command-line arguments for username/password will result in errors. You will have to start an ssh-agent and import your private key so the release plugin can access the GitHub repository and configure the password for in your ~/.m2/settings.xml as described below.

Instead of listing username/password on the command line, you may also specify these in ~/.m2/settings.xml as follows:

<settings xmlns=""

      <id></id> <!-- For parent 1.397 or newer; before this use id -->


You may also follow these instructions to encrypt the password stored in settings.xml. Once you are done with this run mvn deploy to verify that your credential is correctly recognized by Maven.

Additionally, note that your settings.xml file may need extra configuration for publishing the plugin. See here.

Also consider these tips before making a plugin release.

The released plugin should show up in the update center within eight hours.

You will likely need to add your new release info to the Changelog section of your Jenkins plugin wiki page.

Working around common issues

These are some common issues that can occur when releasing a plugin.
If you did release your plugin successfully but are having problems, see also the "Help!" section at the end of this page.

The release process created a "SNAPSHOT" version / Using git version or around
 After cd-ing to your plugin git repo folder, run the maven release commands this way, forcing version 2.5 of maven-release-plugin; alternatively, proceed to the next work-around topic right after this one:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform
git push (should your git status still be "dirty")

Please keep this wiki topic at the beginning of hereby work-arounds, for top visibility purposes.

No prepare commits in git
 Should the previous (related) work-around not suit you, update maven-release-plugin to 2.5 version. See: jenkinsci-dev maillist
If a release only deploys snapshots consider upgrading the maven-scm-provider-gitexe to 1.9.1 or more (see more details.)

or running following command may make your maven-release-plugin work correct (this changes output format of git status).

git config --global --add status.displayCommentPrefix true
If a release fails with the following error, that means the version number for your plugin in pom.xml does not end with -SNAPSHOT. Add this suffix and commit the change, then try again.
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] You don't have a SNAPSHOT project in the reactor projects list.
If changes to your pom.xml seem to be having no effect, try one of these to clear out any intermediate files and start over:
mvn -Dresume=false release:prepare release:perform
mvn release:rollback
mvn release:clean
Releasing failed due to errors relating to Javadoc?
If you see something like this when releasing, including lots of Javadoc errors you can't actually fix, because they're part of the Messages class...
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.8:jar (attach-javadocs) on project <plugin-artifact-id>:
 MavenReportException: Error while creating archive:
... lots of Javadoc errors here ...

..then it's probable that you're building your plugin with Java 8, which has a tool called DocLint enabled by default.

You need to disable DocLint by adding the following to your pom.xml. Merge into the existing build.plugins section, if there is one.

My release failed and I want to redo it from scratch
When a release fails in the middle, you unfortunately have to manually cancel out some of the side-effects Maven has caused. See this e-mail for details. The easiest way out is to forget about the botched release and simply move on to the next release number.
Subversion 1.6 authentication problem
Subversion 1.6 has a known problem with the --non-interactive switch that Maven uses, in that the presence of this switch prevents Subversion from accessing your authentication credentials. See this thread for more background discussion.
You can verify whether this is the cause of your problem by comparing the behavior between svn ls --non-interactive and svn ls Once verified that this is the root cause, tell Subversion to store the password in plain text

Additionally you need to check that you are not accessing the subversion repository with the "guest" user. So try svn ls --username YOURNAME . If it asks for your credentials then simply give it and retry.

OutOfMemoryError: Java heap space
If the release fails because Maven runs out of heap space, you may need to increase its limit by defining the MAVEN_OPTS environment variable. For example, in a bash shell, you could add the following to ~/.profile:
export MAVEN_OPTS=-Xmx300m

If you are running Maven inside IntelliJ 9.0.1, its setting for Maven > Runner > VM Parameters applies to only the parent Maven process, but it may be a child Maven process that is running out of memory. Furthermore, if you are running IntelliJ on MacOSX 10.6, normal environment variables, i.e., exported from ~/.profile, are not seen by apps launched from Finder. So, to increase the heap limit of child Maven processes in IntelliJ, you can configure MAVEN_OPTS in /etc/launchd.conf instead. Create or edit the file, e.g. sudo vi /etc/launchd.conf and add:

/etc/launchd.conf on MacOSX
setenv MAVEN_OPTS -Xmx300m
Error deploying artifact: Connection failed: Unable to connect to
If the deployment fails it might be trying to write to a legacy repository. The instructions above and in the migration page should help with setting the correct target repository.
HTTP 401 when transferring a file to the Jenkins Maven repository
If, when running mvn release:perform, you get an error message similar to the following one, there are a few possibilities:
  • Your password is incorrect
  • You haven't added your credentials to your ~/.m2/settings.xml file as described above.
  • The ID of the repository as specified in POM (which is normally inherited) doesn't match the ID in ~/.m2/settings.xml. To verify this, run mvn help:effective-pom and look for the <distributionManagement> element. For example, see this. This is because earlier versions of the plugin parent POM had this kind of problems. The easiest solution is bump up the parent POM to 1.409 or later. If you need to keep the parent version as is, then add additional <server> entry in your settings.xml with all the variations of the IDs.
  • Your plugin with this version was already released, and you are trying to release another one with the same version (check it here).
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project sbt:
Failed to deploy artifacts: Could not transfer artifact org.jvnet.hudson.plugins:sbt:hpi:1.0 from/to (
Failed to transfer file:
Return code is: 401 -> [Help 1]
Make sure PW encryption is correct:
Make sure you use Maven 3
If release:prepare fails with the following error, you are most likely using "Cygwin" on Windows. There is a failure of path translation somewhere between Maven and the Cygwin Subversion client. The easiest way around this is to install a native Windows Subversion client (eg. Win32Svn) and re-run from a DOS/CMD window.
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive commit
       --file C:\DOCUME~1\username\LOCALS~1\Temp\maven-scm-1876439793.commit
       --targets C:\DOCUME~1\username\LOCALS~1\Temp\maven-scm-7190199490958000758-targets"
[INFO] Working directory: D:\home\ed\projects\hudson\plugins\lavalamp
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
svn: '/cygdrive/d/home/username/projects/hudson/plugins/lavalamp/D:/home/username' does not exist
If a release fails with either of the following errors, that means you don't have hudson/plugins/pom.xml installed in your local repository. Run mvn -N install in the plugins directory and retry a release.
[INFO] Executing: mvn deploy
--no-plugin-updates -DperformRelease=true
    [INFO] Scanning for projects...
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] Error building POM (may not be this project's POM).

    Project ID: null:xxxxxx:hpi:N.N
[INFO] Scanning for projects...
       [INFO] ------------------------------------------------------------------------
       [INFO] ------------------------------------------------------------------------
       [INFO] Failed to resolve artifact.

    GroupId: org.jvnet.hudson.plugins
       ArtifactId: plugin
       Version: 1.212

    Reason: Unable to download the artifact from any repository


    from the specified remote repositories:
          central (
Could not find maven-hpi-plugin jar
If release:prepare fails with an error like the following:
[ERROR] Unresolveable build extension: Plugin or one of its dependencies could not be resolved:
Could not find artifact in central (

You may need to update your local settings.xml. (A build might work, but not a release:prepare.) See here.

Subversion 409 Conflict
If a release:perform fails with an error like the following, retry mvn release:perform later. We don't know the root cause of this problem, but the problem does seem to disappear after a while.
[INFO] [INFO] Error deploying artifact: Connection failed: Unable to connect to
[INFO] svn: The specified baseline is not the latest baseline, so it may not be checked out.
[INFO] svn: CHECKOUT of '/svn/maven2-repository/!svn/bln/1348162': 409 Conflict (
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] For more information, run Maven with the -e switch
[INFO] [INFO] ------------------------------------------------------------------------
git push hangs
Stackoverflow offers suggestions on how to correct this at
For TortoiseGit users
If you use TortoiseGit as a Git client, do followings to have maven to run with TortoiseGit settings.
  1. Write the username/password of your account in settings.xml (See above for details).
    • Passing username/password in the command line seems result that SSH client recognizes the username as the hostname, and fails to connect.
  2. Add the path of msysgit to PATH environment variable. You can see the path to msysgit in TortoiseGit>Settings>General, "Git.exe Path"
    set PATH=C:\Program Files\Git\bin
  3. Set the path of TortoisePlink.exe (in the bin directory of TortoiseGit) to GIT_SSH environment variable.
    set GIT_SSH=C:\Program Files\TortoiseGit\bin\TortoisePlink.exe
  4. Start pageant, and load putty key (ppk).
    pageant path\to\id_rsa.ppk
  5. Run release command without username/password
    mvn release:prepare release:perform

Frequently asked questions

What should the Java package name be?

Most plugins use org.jenkinsci.plugins.*, but if you'd like to use your own package name, feel free to do so.

Help! My plugin is not showing up in the update center.

  1. First, check the release Maven repo and see if your plugin is listed there. If not, your release process failed, and it never left your PC. If you can't resolve this issue, capture the output from mvn release:prepare release:perform and send it to the dev list.
  2. If your new version appears in the SNAPSHOT repo (rather than the "release" repo), see the "Working around common issues" section above
  3. Check if your new version is in This file is updated every 4 hours (plus mirror propagation time), so there's some delay before your new version appears here.
  4. If your plugin appears there but not in your Jenkins update center, visit Manage Plugins / Advanced and click "Check Now" to make Jenkins retrieve the latest update-center.json data.
  5. Search for your plugin's artifact ID in the Update Centre build log to see whether your plugin has been included, or why it has been excluded.
  6. Check the INFRA project for existing issues, or ask on IRC or the developers' mailing list; otherwise you can open an INFRA issue
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment