The following parameters are available to create this step:
Artifact name, in the form
Select the latest version ( Latest ), the exact version of the artifact ( Exact ), or a version range ( Range ). Version is in the form:
Retrieve to directory
If you want to retrieve this artifact version to a specific directory location, select the check box, then specify the full path to the directory where you want to retrieve this artifact version.
Use the drop-down menu to select one of the following options:
Retrieved Artifact Location Property
Name or property sheet path used by the step to create a property sheet. This property sheet stores information about the retrieved artifact versions as XML in the
This example shows how to retrieve the location of the retrieved
Enter search filters, one per line, applicable to querying the CloudBees Flow database for the artifact version to retrieve.
The order of dependencies registered for an artifact version are significant.
Consider this scenario:
A depends on B (any version) and C [1.0, 2.0)
B depends on C (any version)
C versions 1.0, 2.0, and 3.0 exist
When retrieving A, the dependency algorithm evaluates B first. The algorithm finds that the max version of B depends on any version of C, so the algorithm looks for max version C and finds C 3.0. Because this chain is satisfied, the algorithm returns to A and evaluates its next dependency "C [1.0, 2.0)". This results in matching C 1.0.
The returned artifacts are: A, B, C 1.0, and C 3.0.
Consider if the A dependency is changed to:
A depends on C [1.0, 2.0), B (any version)
The algorithm will choose C 1.0 first. Then the algorithm evaluates B, determines that its "C (any version)" is satisfiable by the already-chosen C 1.0.
The returned artifacts are A, B, and C 1.0.
|In the version range syntax  indicates inclusive, and () indicates exclusive.|