Performing a Plugin Release

View the index of available developer guides


  1. Make sure you have permissions to release the plugin. See this guide to learn more details

Artifactory Credentials for Maven

You will need to tell Maven your credentials to access Artifactory. Log in to Artifactory, and from your profile, obtain the encrypted password.

Create the file ~/.m2/settings.xml (~ representing your user home directory, e.g. /home/yourname or C:\Users\yourname) if needed, and make sure it contains the <servers> element as shown below:

<settings xmlns=""

      <id></id> (1)

1 This is not a valid host name anymore, but still the ID used by default in the Jenkins plugin parent POM. You may need to add additional <server> entries if your plugin POM overrides the inherited Maven <distributionManagement>, but this should be rare.

Set up GitHub to accept your SSH key

Maven Release Plugin will automatically push to the repository when performing a release, so you need to set up GitHub to accept your SSH key.

See the GitHub help on SSH for more information.

Performing the release

With GitHub and Maven credentials set up, performing a release should be as easy as running the following command:

mvn release:prepare release:perform


First, make sure your plugin uses a reasonably up to date parent POM. This will prevent the vast majority of problems in releasing the plugin, such as outdated Maven plugins, or obsolete host names.

The upload to the Maven repository fails with "401 Unauthorized"

Unauthorized means that your credentials were invalid, or not sent by Maven.

Make sure you’ve updated your encrypted password since the last time you changed your password on the account app.

The upload to the Maven repository fails with "403 Forbidden"

This means you don’t have permission to upload to the specified path.

Learn more about how to request upload permissions, and confirm that the path you’re allowed to upload to matches the actual upload attempt.

Further troubleshooting help

If none of the provided solutions help, send an email to the Jenkins developers mailing list and explain what you did, and how it failed.