Have a question? Want to report an issue? Contact JFrog support

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


titleArtifactory HA Plugins Directory

If you are working with an Artifactory 5.x a High Availability cluster your user plugins should be added to the master node under:


And they will be propagated to the entire cluster.


If working with Artifactory 4.x High Availability cluster, your plugins should go under:



Any file name ending with .groovy is loaded on startup. You can have multiple plugin files which are loaded in alphabetical order. Callbacks defined in plugins are called by the order they were loaded.


Reloading Plugins

By default, plugins are not reloaded after Artifactory has started-up. You can configure Artifactory to automatically detect plugin changes changes on disk  disk or new plugin files and automatically reload them them in runtime  runtime (plugin removals are not detected), or reload plugins using the REST API.To do this

Auto Reload

To automatically reload plugins that have changed, set the number of seconds to check for plugin updates to a number greater than 0, by changing the following property in ${ARTIFACTORY_HOME}/etc/artifactory.system.properties, or by specifying the property with -D to the JVM running Artifactory:


titleDisabling Plugin Reloading for Production

Ensure plugin auto-reloading is disabled in a production environment.

Reloading Plugins via REST API

You can reload plugins using the Reload Plugins REST API endpoint. 

Plugins Lib Directory

If your plugin requires any external dependencies, you can place them under the ${ARTIFACTORY_HOME}/etc/plugins/lib directory.