Artifact Dependencies
Administration > <build configuration> > Artifact Dependencies
Artifact Dependencies
If the build configuration contains artifact dependencies, the following information is presented for each dependency:
| Option |
Description
|
Artifacts source
|
The dependency in the following format:
<Project name>::<Build configuration name> <Where the artifact is taken from>
|
Artifacts path
|
The path to the artifact dependency on the server.
|
Destination path
|
The target location of the dependency on the build agent.
|
| Edit |
Click this link to modify the selected dependency.
|
Delete
|
Click this link to remove the selected dependency.
|
Add / Edit Dependency
| Option |
Description
|
Add new dependency
|
Click this link to specify the artifact dependency.
|
Depend on
|
Specify the build configuration that the current build configuration should depend on.
|
| Get artifacts from |
Specify the type of build, from which the artifacts should be taken. The following options are available:
- Last successful build
- Last pinned build
- Last finished build
- Build number
 | Note
When selecting the build configuration, take your clean-up policy settings into account. Builds are cleaned and deleted on a regular basis, thus the build configuration could become dependent on a non-existent build. When artifacts are taken from a build with a specific number, then the specific build will not be deleted during clean-up.
|
|
| Build number |
Use this field to specify the exact build number of the artifact. This field is enabled, if the Build number option is selected in the Get artifacts from field.
|
| Artifacts path |
Specify the artifact's path to the "source" build. The path should be relative to the artifacts directory of the "source" build. The path can either match a specific file, or wildcards (*, ?) can be used to include multiple files and directory names. Note the "." that separates the file name from the extension is not matched by either "*" or "?" and, if necessary, should be included in the wildcard directly. Please also note that downloaded artifacts will have the same directory structure as the source artifacts.
For example: use a/b/*.* to download all files with extension from a/b directory of the source build. If there is a a/b/c/file.txt file in the source build artifacts, it will be donwloaded into the file: DestinationPath/a/b/c/file.txt |
| More artifacts |
Click this link to open an additional text field, where you can specify the path to additional artifacts.
|
Destination path
|
Specify the destination path on the agent where downloaded artifacts should be placed. If the path is relative, it will be resolved against the build checkout directory. If needed, the destination path can be cleaned before downloading artifacts.
|
| Clean directory before downloading artifacts |
Check this option to delete the content of the destination directory before copying artifacts. |
| Save |
Preserve changes and close the page.
|
See also:
