The Gradle Artifactory Plugin supports all versions of Gradle and is available from the Gradle Plugins Gallery.
The plugin supports both Gradle Configurations and Publications for deploying artifacts to Artifactory.
Getting Started Using the Plugin
The following 3 steps add the Gradle Artifactory Plugin to your Gradle build script.
Step 1: Apply the plugin
Step 2: Add the "artifactory" closure
Add the bellow "artifactory" closure, replacing your Artifactory URL, publication and resolution repositories and also your deployer and resolver Artifactory credentials.
Step 3: Run the build
The next thing you want to do is to tell the plugin which of the build artifacts you'd like to deploy to Artifactory.
Using the Correct Plugin ID
The Gradle Artifactory Plugin ID depends on two parameters:
To simplify these documentation pages, the plugin ID will be referred to using a <PLUGIN ID> placeholder.
This placeholder should be replaced with the plugin IDs listed in the table below:
The Artifactory Plugin DSL
The Gradle Artifactory plugin can be configured using its own Convention DSL inside the
The syntax of the Convention DSL is described below:
The Artifactory Project Publish Task
The Artifactory Publishing Plugin creates an
You can configure the project-level task directly with the task's
Controlling the Published Modules
To control which modules of a multi-module build, are published to Artifactory you can:
Controlling the Build Name Number in BuildInfo
By default, BuildInfo is published with a build name constructed from the name of your root project and a build number that is the start date of the build.
The above properties are specified as standard Gradle properties.
You can also control the build name and number from within the Convention object DSL as shown at the end of the Convention DSL syntax above.
Project examples which use the Gradle Artifactory Plugin are available here.
Watch the Screencast
To see the Gradle Artifactory Plugin in action please watch this screencast.: