Snapshot dependency build configurations to trigger at same time

Hi Rahul

Snapshot dependencies make a build chain, so dependent build always waits for previous build execution (and usually uses its artifatcs).
To run two builds in parallel you can make them depend on some additional empty configuration.

Michael

Hello Michael,


Thanks for your comments. We have been working on that implementation and hopefully will work.


Solution: Create a dummy build project Build-Parent and make Build-A and Build-B have snapshot dependency on it.


Thanks,


Rahul

I have been trying the method mentioned in the previous post and have run into issues. In continuance from the above scenario this the error I am getting.


Build-A and Build-B has a snapshot dependency on Build-P. Build-P is triggered on a svn commit and it checkedout the source at revision 100. In the meantime the revision number was bumped to 103 because of multiple commits. And now when I run Build-A and Build-B it is using revision 103 and not 100.


On reading this link http://confluence.jetbrains.net/display/TCD6/Dependent+Build (testing the behaviour in TC6 now) it seems TC ensures the sources are same.

Can someone highlight here how does Teamcity compare the sources? Is it a binary compare or it simply goes by revision number (in case of subversion)?


Thanks,


Rahul

Hi Rahul

The server should remember a timestamp when the first build in a chain is started, and then checkout corresponfing revisions for all dependent builds.

Could you post teamcity-server.log and teamcity-vcs.log please.

Michael

Hello Michael,


I am using "Checkout at agent" mode because I need to have some svn info from the workspace. Do you think that it needs to be checked out on server?


Thanks,


Rahul

It doesn't depend on server/agent side checkout mode.
But without the logs it's hard to say what's wrong there.