I watched quite a few of these discussions until I was successful.
Our build process (on TeamCity 6.5.5) creates two folders: A and B.
We are currently setting up folder B for deployment (artifact path. \ B => B-% build.number% .zip). However, it was decided that folder A should be included as an archive in zip of B. That is, after assembly, B-2.0.0.zip should look like this:
B-2.0.0.zip file 1 ... file n A.zip file a1 ... file an
To accomplish this, I added an artifact path. \ A =>. \ B \ A.zip before the existing zip rule for B, so our artifact paths look like this:
.\A => .\B\A.zip .\B => .\B-%build.number%.zip
However, while A.zip is being created (I see it in folder B after the build), it is not added to the B.zip archive. I looked at the build result, and the artifacts were created in the expected order.
Honestly, I'm at a dead end. Any insight would be well and appreciated. I could potentially modify the construction of the script to execute this, but I would prefer, if at all possible.
Thanks in advance.
Edit (2/24/12): As for further research, it seemed that I had a problem creating the A.zip file as a temporary file and fell into place after creating all the artifacts.
So, I tried to reorder my artifact paths as follows:
.\B => .\B-%build.number%.zip .\A => .\B-%build.number%.zip\A.zip
I thought this would add A.zip to B.zip. Instead of a nested archive, a folder named A.zip is created. Am I just looking at the limitation of TeamCity's inability to embed archives?