using artifacts from a non-check out directory created by build script?

In order to consolidate some assemblies in multiple folders, I've created a nant build script that will move the assemblies into a non-check out directory that the script creates.
How would I instruct TeamCity to use this directory for artifact dependencies?

2 comments
Comment actions Permalink

I've just run into this issue myself.  I cannot publish artifacts from a directory that is not within the checkout directory.  Is there a way around this?

Whether I refer to the files relatively or directly, they end up not publishing to TeamCity's server.  In order to keep checkout directories clean of logs and results files, we decided a while ago to publish them to a parallel directory.  It would be nice to not have to change this system just to make it work better with TeamCity.  

0
Comment actions Permalink

Figured out the workaround myself.  I changed the checkout directory to the parent of what I wanted as the checkout directory then used the checkout rule +:.=>latest   (latest being the name of the checkout directory I originally wanted)

So if anyone's searching around for this question, here's your answer.  

0

Please sign in to leave a comment.