tag:blogger.com,1999:blog-4863981320393275450.post4965926537825509448..comments2008-12-30T23:09:29.111-08:00Roy Osherovehttp://www.blogger.com/profile/10889682616497587473noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4863981320393275450.post-79419799239522825462008-12-30T23:09:00.000-08:002008-12-30T23:09:00.000-08:00Soon Hui,<BR/><BR/>Ohad is correct. <BR/>You need to optimize your situation. In the continuous integration cycle, do the compilation and unit tests only. You have to have <B>quick</B> feedback. <BR/><BR/>The integration tests can run on a nightly cycle, so you can come to work in the morning and see the result. Automate whatever your can.Gil Zilberfeldhttp://www.blogger.com/profile/18210181375618736629noreply@blogger.comtag:blogger.com,1999:blog-4863981320393275450.post-42161070118366601782008-12-30T11:51:00.000-08:002008-12-30T11:51:00.000-08:00Soon,<BR/>How about taking the time needed to merge the project files (how long should it take one, two days week?) and than run the integration tests in nightly build while the unit tests will run each check in. <BR/><BR/>I think that in that case stopping the daily development race and taking the time to make the development environment better will pay off down the line.Ohadhttp://www.blogger.com/profile/10873422919971340819noreply@blogger.comtag:blogger.com,1999:blog-4863981320393275450.post-23514934126330199122008-12-30T03:17:00.000-08:002008-12-30T03:17:00.000-08:00Great post.<BR/><BR/>My situation is this: every developer has his own csproject files, and this make merging them somewhat hard. Not only that, the integration tests take 3 hours to run.<BR/><BR/>Guess there is no way for me to do continuous integration, though.Soon Huihttp://www.blogger.com/profile/12990238997406388445noreply@blogger.com