Using Artifactory to store plugins
JFrog Artifactory can now be used as a proxy for plugins that are currently hosted on Nexus, allowing it to act as a mirror for your plugin repository in secure, air-tight environments.
To configure JFrog Artifactory as the plugin repository, update the xl-release.conf
file by modifying the xl.features.plugins.servers.${serverName}.server-type
property:
- If set to "nexus", Nexus will be used as the plugin repository.
- If set to "artifactory", JFrog Artifactory will be used as the plugin repository.
Additionally, update the url
, username
, and password
fields to match the Artifactory server's credentials and URL. This configuration will ensure that your plugin manager seamlessly transitions to the new repository.
Here's a sample:
To enable artifactory, edit xl-release.conf
to set xebialabs-plugins.server-type
to "artifactory" and change the credentials.
xl {
features {
plugins {
repositories {
xlr-official {
enabled=true
nexus-group-id="com.xebialabs.xlrelease.plugins"
nexus-metadata-artifact {
artifact-id=xlr-plugins-metadata
group-id="com.xebialabs.xlrelease.plugins.metadata"
}
nexus-repository-id=official-plugins
repository-type=nexus-by-group-id
server-ref=xebialabs-plugins
xl-component=xl-release
}
}
servers {
xebialabs-plugins {
server-type=artifactory
url="http://localhost:8082"
credentials {
password="{aes:v0}1QJioKHIh6Edykb1ixVNAgk/BEgGQf3k3xKrOMDOc+c="
username=admin
}
}
}
}
}
}
For more information, see how to migrate from Sonatype Nexus repository to JFrog Artifactory.