The JFrog Artifactory Deployer task uses the JFrog CLI and facilitates working with VSTS and Artifactory, effectively, on any build tool such as Maven, Gradle and others, for any packaging format such as NuGet, npm and others.
To use it, you need to configure a new service that points to an Artifactory instance as displayed in the following screenshot.
 |
Note
Parameter values with spaces should be enclosed within quotation marks.
Field | Description |
|---|---|
Click "Manage" to set the Artifactory instance to which you want to deploy artifacts. | |
The target repository and path within that repository to which you want to deploy artifacts. Note that you can use environment variables such as | |
When checked, you can override credentials provided by the service. | |
User name to use if you have checked Override Credentials. | |
Corresponding encrypted password to use if you have checkedOverride Credentials. | |
Path to the Artifactory CLI in your VSTS team project code repository. | |
Path to the artifacts you want to deploy. You may use environment variables and wild card characters. | |
Properties to attach to deployed artifacts. | |
If checked, build information will be created. |
In the example above, we are deploying any NuGet package containing "VSODemo" in its name that is located in the build directory or subfolder of the Artifactory configured as service “ArtifactoryGC” in the repository called “nuget-stage-local” with path “JFrog/MyTestProject/<BuildNumberValue>”. Some properties will be attached and the build information provided.
Once the build is complete, you can view its details in Artifactory as displayed below:
 |
You can also view details for each build including a link back to the VSTS build summary:
 |
 |
 |