Place your plugin files under
Artifactory HA Plugins Directory
If you are working with a High Availability cluster your user plugins should be added to the primary node and they will be propagated to the entire cluster.
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.
By default, plugins are not reloaded after Artifactory has started-up. You can configure Artifactory to automatically detect plugin changes on disk or new plugin files and automatically reload them in runtime (plugin removals are not detected), or reload plugins using the REST API.
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
$JFROG_HOME/artifactory/var/etc/artifactory/artifactory.system.properties, or by specifying the property with -D to the JVM running Artifactory:
Deleting or renaming plugin files while auto-reloading is active is not fully supported and requires an Artifactory restart.
Disabling Plugin Reloading for Production
Ensure plugin auto-reloading is disabled in a production environment.
Reload Plugins with REST API
You can reload plugins using the Reload Plugins REST API.
Plugins Lib Directory
If your plugin requires any external dependencies, you can place them under the