Using Artifact Dependencies

Hello:

I have a build that is dependent on an artifact (a jar file named nwf.jar) produced from another build. So, I am trying to create an artifact dependency. In the build that produces the nwf.jar I configure the dependency as such:

3rdparty/nwf/nwf.jar => 3rdparty/nwf

When the build finishes I see that there is in fact an artifact correctly created:

[16:28:34]: Publishing artifacts
[16:28:34]: [Publishing artifacts] Paths to publish: [3rdparty/nwf/nwf.jar => 3rdparty/nwf, teamcity-info.xml]
[16:28:34]: [Publishing artifacts] Publishing artifacts '3rdparty/nwf/nwf.jar' to 3rdparty/nwf
[16:28:34]: Build finished


And I have verified this on the file system.


Now I would like to 'inject' the dependency into the other build. In the 'Edit Artifact Dependency' dialog, I:


-Select the build with the artifact
-Select 'Last successfull build'
-Specify the artifact path '**/nwf.jar' (I have tried others like 3rdparty/nwf/nwf.jar. That didn't work either.)
-Specify the destination path '3rdparty/nwf'


When I check the artifact dependencies, I get the following:


[16:34:47]: Dependency resolving started...
[16:34:47]: Downloading artifacts from: http://nwf-rtp-build1:8111
[16:34:47]: Failed to download artifact dependency <NWF :: NWF Continuous Build (last successful build)>: Download of artifact 3rdparty/nwf/nwf.jar from build configuration <NWF :: NWF Continuous Build (last successful build)> (source path **/nwf.jar) failed: missing artifact
[16:34:47]: Failed to download 1 of 1 artifact dependencies
[16:34:47]: Dependency resolving finished


I also ran the build, just to see what would happen, and I get:


[16:36:33]: Failed to download artifact dependency <NWF :: NWF Continuous Build (last successful build)>: Download of artifact 3rdparty/nwf/nwf.jar from build configuration <NWF :: NWF Continuous Build (last successful build)> (source path **/nwf.jar) failed: missing artifact
[16:36:33]: Artifacts resolving failed: Failed to download 1 of 1 artifact dependencies



What am I doing wrong?

Thanks,
Richard.

5 comments
Comment actions Permalink

What version of TeamCity you are using? Could you please attach screenshot of the Artifacts tab with all nodes expanded of the build from which you want to download dependencies?

0
Comment actions Permalink

Sorry about that: 4.0.2 (build 8222)

ArtifactsSS.JPG

Here's the dependencies page of the dependent build, as well:

DependenciesSS.JPG

Thanks,
Richard.

0
Comment actions Permalink

I reproduced this bug. It is caused by # in the build number: 115 (change #90...). It looks like ivy does not like # in the build numbers, if you can remove it download will work. Please watch/vote for this issue: http://www.jetbrains.net/tracker/issue2/TW-8075

0
Comment actions Permalink

Hey Pavel:

That worked.

Thanks so much for the quick resolution of this problem,
Richard.

0
Comment actions Permalink

Hi,

I'm using TeamCity v4.5 build 8944 and have the same problem but I'm not using ivy.

In my case I have a dependency on latest pinned build and it was a '/' in the build number string that made the artifact copy fail. Changing to a '_' fixed the problem!

0

Please sign in to leave a comment.