An artifact task lets you search the library of binaries in different repositories that you can deploy on a virtual machine.

About this task

When you include an artifact task in a stage, you can run a pipeline execution every time you develop new code that affects that artifact. The search output parameter from varied source repositories is always the same, which includes a repository name, a download URL, and size information, if available.

Figure 1. Sample Artifact Task
Sample artifact task showing search types and input properties.



  1. Select Release Automation.
  2. Select the pipeline to configure from the Pipeline tab.
  3. Select Edit > Stages.
  4. Select Add Task.
  5. Select Artifact from the Category drop-down menu.
  6. Assign the Provider from the drop-down menu.

    The provider is the repository that you configured.

  7. Enter a name for the artifact task and click OK.
  8. Select the new task from the stage column.
  9. Confirm to save the pipeline for configuration.
  10. Select an Artifactory repository from the drop-down menu.
  11. Determine a search type and click Validate to verify that the artifact exists in the repository.

    The search type depends on your repository and artifact. If the search shows that an artifact does not exist, verify that the search parameters are accurate.

    For example, you can search for the Maven artifacts using the gavc search type.

    Search Type



    Provide the group ID, artifact ID, version ID, and classifier parameters for the search.

    • The group ID is the org that published the artifact.

      For example, org.springframework.

    • The artifact ID is the identifier of the artifact.

      For example, travel.

    • The version ID parameter supports the LATEST and version-SNAPSHOT keywords.

      For example, enter 4.1-SNAPSHOT to get the snapshot of a version.

    The classifier supports the wild card character asterisk (*). For example, release*, *release*, or *.


    Provide the repository name and path parameters for the search.

    • The name parameter supports the wild card character asterisk (*).

      For example, test*, test.*, *.jar, or *.

    • The path parameter supports the wild card character asterisk (*) for local repositories.

      For example, path/*/release searches under the path directory in the /test/release and /dev/release folders for the artifacts only in those folders.

      Each wildcard (*) represents one level in the folder structure.


    Defined in the Artifactory server to tag artifacts with custom user properties.

    These properties can be any string values. An artifact can have multiple properties and these properties can have multiple values. You can use these properties instead of the actual group ID, version, or specific path to locate an artifact in the repository.

    For example, the Property field can be artifactory.licenses and the Value field can be BSD .


    Builds cannot be created in the Artifactory user interface. A build must be pushed from your CI server to the Artifactory user interface.

    • The build Name is the name of the job that is run on your CI system.

      For example, Jenkins-release.

    • The build Number supports the LATEST or a build status keyword .

      For example, you can search for builds with the Prod status.

    • The name lets you filter an artifact from the list of artifacts in a specific build.

      For example, public-API.jar or public-*.jar

  12. Provide a unique name prefixed with a dollar sign ($) to bind to for the Output Parameters.
  13. (Optional) Click Add to include another artifact and configure the parameters.
  14. Click Save.