build failing on dependency

I'm trying to take dependent assemblies from other projects in other repositories and add them to another project build. Can I not have TeamCity copy them to the current project's bin folder so that it builds?

I get the following error:
Failed to download artifact "trunk/src/bin/*.dll" from LibraryProject :: Compile LibraryProject (last successful build). File not found.

The path above is relative to the LibraryProject checkout directory.

What am I doing wrong?

5 comments
Comment actions Permalink

No one is using the artifact dependency UI ?

Here is what I've done.
On LibraryProject build, I've set artifact path to "trunk/src/bin/*.dll"
On ProductProject, I've set artifact dependency to LibraryProject using path "trunk/src/bin/*.dll" and the destination path to "trunk/src/bin/".

I get the error I posted previously. Any help??

0
Comment actions Permalink

Realized that the source path is in the root of the artifact build, so I just needed the file name or just "*.dll".

Now, how would I share API tools that are not built, but just in a library repository?

0
Comment actions Permalink

I use the artifact dependency UI in several configurations, but not across machines. If your "library repository" is simply a file system that can be accessed from the build agent, you should be able to add a step to your build process to bring in what is needed. If you want to really organize all your dependencies, I would take a look at Ivy and this article to see if employing that tool might help you long-term.

0
Comment actions Permalink

How would I access 3rd party assemblies that are on a shared drive and not in another build? The machine TC sits on has access to the shared drive but it doesn't find the assembly.

0

Please sign in to leave a comment.