このフィールドは、選択した場合に表示されます。build with specific build numberin theから成果物を入手するlist. Specify here the exact build number of the artifact.
このフィールドは、選択した場合に表示されます。last finished build with specified tagin theから成果物を入手するlist. Specify here the tag of the build whose artifacts are to be used. When resolving the dependency, TeamCity will look for the last successful build with the given tag and use its artifacts.
Each rule specifies the files to be downloaded from the "source" build. The ソース・パス should be relative to the artifacts directory of the "source" build. The path can either identify a specific file, directory, or use wildcards to match multiple files. Antのようなワイルドカード are supported. Downloaded artifacts will keep the "source" directory structure starting with the first * or ? . DestinationPath specifies the destination directory on the agent where downloaded artifacts are to be placed. If the path is relative (which is recommended), it will be resolved against the build checkout directory. If needed, the destination directories can be cleaned before downloading artifacts. If the destination path is empty, artifacts will be downloaded directly to the checkout root.
ArchivePath is used to extract downloaded compressed artifacts. Zip, 7-zip, jar, tar and tar.gz are supported. ArchivePath follows general rules for ソース・パス : ant-like wildcards are allowed, the files matched inside the archive will be placed in the directory corresponding to the first wildcard match (relative to destination path) For example: release.zip!*.dll command will extract all .dll files residing in the root of the release.zip artifact.
The artifacts placed under the .teamcity directory are considered hidden. These artifacts are ignored by wildcards by default. If you want to include files from the .teamcity directory for any purpose, be sure to add the artifact path starting with .teamcity explicitly.
where TEAMCITY_HOST is hostname or IP address of your TeamCity server (without port and servlet context). As USER_ID/PASSWORD you can use either username/password of a regular TeamCity user (the user should have corresponding permissions to access artifacts of the source build configuration) or system properties teamcity.auth.userId/teamcity.auth.password .