IntelliJ Platform SDK DevGuide

Edit page

Publishing Plugins with Gradle

Once you have configured Gradle support, you can automatically build and deploy your plugin to the JetBrains Plugin Repository. To do so, you will need to have already published the plugin to the plugin repository. For detailed information, please see the guide to publishing a plugin.

2.0 Add your account credentials

In order to deploy a plugin to the plugin repository, you will first need to supply your JetBrains Account credentials. These are typically stored in the Gradle properties. It is crucial that you do not check these credentials into source control.

Place the following information inside a file called under your project’s root directory, or inside GRADLE_HOME/

intellijPublishUsername="YOUR_USERNAME_HERE" intellijPublishPassword="YOUR_PASSWORD_HERE"

Then refer to these values in publishPlugin task in your build.gradle file:

publishPlugin { username intellijPublishUsername password intellijPublishPassword

If you place a file in your project’s root directory, please ensure that this file is ignored by your version control tool. For example in Git, you can add the following line to your .gitignore file:

Alternately, you may decide to create a default template, and instruct git to ignore any future changes to that file. To do so, check in the default template and execute the following command:

git update-index --assume-unchanged

If your project already has a custom file, you may create a custom *.properties file, and load it manually. For example:

apply from: "/path/to/"

2.1 Configure your plugin

The gradle-intellij-plugin provides a number of configuration options for customizing how Gradle builds your plugin. One of the most important is the version. By default, if you modify the version in your build script, the Gradle plugin will automatically update the <version> in your plugin.xml file.

The Gradle plugin will also update the <idea-version since-build=.../> values within the plugin.xml file to match the intellij.version, valid until the last release in the current major version, however you can disable this feature by setting the intellij.updateSinceUntilBuild option to false.

apply plugin: 'org.jetbrains.intellij' intellij { version '15.0.1' pluginName 'idear' intellij.updateSinceUntilBuild false //Disables updating since-build attribute in plugin.xml } group 'com.jetbrains' version '1.2' // Update me!

When you run gradle runIdea with a build script containing the above snippet, Gradle will download the appropriate version of IntelliJ IDEA from either a Snapshot (time-based) or Release (version based) repository, configure the plugin sandbox, install your plugin, and launch a new instance of the IDE. This task can be run directly from the command line, without any prior tooling assistance.

For best results, plugin developers should build against a fixed version, rather than LATEST-TRUNK-SNAPSHOT. For information about available versions of the IntelliJ Platform, you may consult the following URLs for the most recent updates:

2.3 Deploy your plugin

The first step when deploying a plugin is to confirm that it works correctly. You may wish to verify this by installing your plugin from disk on a fresh instance of your target IDE(s). Once you are confident the plugin works as intended, make sure the plugin version is updated, as the JetBrains Plugin repository will not accept multiple artifacts with the same version. To deploy a new version of your plugin to the JetBrains plugin repository, execute the following Gradle command:

gradle publishPlugin

Now check that the most recent version of your plugin appears on the Plugin Repository. If successfully deployed, any users who currently have your plugin installed on an eligible version of the IntelliJ Platform will be notified of a new update available on the following restart.

You may also deploy plugins to a release channel of your choosing, by configuring the property. When empty, this will use the default plugin repository, available to all JetBrains plugin repository users. However, you can publish to an arbitrarily-named channel. These non-default release channels are treated as separate repositories for all intents and purposes. When using a non-default release channel, users will need to add a new custom plugin repository to install your plugin. For example, if you specify 'canary', then users will need to add the repository to install the plugin and receive updates. Popular channel names include:

  • alpha:
  • beta:
  • eap:
Last modified: 25 January 2019