Hi, Peter!
What situation do you have in mind that could cause the compilation to be unsuccessful?
E.g. compilations using a projection when the result of compilation could be totally unpredictive.
Also, compilation can be a time-consuming process, comparing to replacing cache.dat file - so it potentially a longer pause in production operation.
I can't see how deploying/copying the Cache.dat will avoid problems when you have multiple developers or multiple projects on the test server.
I'm not saying that coping cache.dat strategy should be used for a test server. Indeed we can compile the branch on a build/test and then transfer cache.dat to a production if testing goes well.
- Log in to post comments


