Skip to main content
Version: Early Access

Using Artifactory to Store Plugins

Overview​

You can now configure JFrog Artifactory as a proxy for plugins that are currently hosted on the official Nexus repository.

This allows Artifactory to act as a mirror for your plugin repository in secure, airtight environments where Deploy cannot directly access the public plugin repository.

When configured, the Deploy Plugin Manager will fetch plugins from Artifactory instead of Nexus.

Configuration​

To configure JFrog Artifactory as the plugin repository, update the deploy-plugins.yaml file.

  • Set the server-type property for your plugin server to artifactory (instead of nexus).
  • Update the url, username, and password fields to match your Artifactory server’s credentials and URL.

This configuration ensures that the Plugin Manager seamlessly transitions to the new repository.

Example deploy-plugins.yaml​

deploy:
  plugins:
    repositories:
      - enabled: true
        name: xld-official
        nexus-group-id: com.xebialabs.xldeploy.plugins
        nexus-metadata-artifact:
          artifact-id: xld-plugins-metadata
          group-id: com.xebialabs.xldeploy.plugins.metadata
        nexus-packaging-type: xldp
        nexus-repository-id: official-plugins
        repository-type: nexus-by-group-id
        server-ref: xebialabs-internal
        xl-component: xl-deploy
    servers:
      - credentials:
          username: admin
          password: '{cipher}be4adfbc5745d1c78d636c05e03281843296d0052e8eb81b42e2518e0f103216'
        name: xebialabs-internal
        server-type: artifactory
        url: http://localhost:8082

Replace https://artifactory.example.com/artifactory with the URL of your Artifactory server. Replace the encrypted password with one generated for your Deploy environment.

Airtight Environment Use Case​

When using Artifactory as a Nexus proxy:

  • Create a Remote Repository in Artifactory pointing to:
https://plugins.xebialabs.com/nexus/content/groups/official-plugins/

  • Enable caching so that once fetched, plugin artifacts are stored locally.

  • Configure Deploy to point to the Artifactory remote repository using the example above.

Verification Run the following command to confirm that plugins are fetched from Artifactory:

xl pm list

If Artifactory is configured as a proxy, plugins will be cached locally after the first fetch.

For more information, see how to Migrate from Sonatype Nexus repository to JFrog Artifactory.