We check out a working copy to our integration server, then use a file
comparison/copy tool to go from there to production. For incremental
releases, this means we just do a "svn update" to the integration server -
no need for a full checkout each time.
Ant or even xcopy can do the upload to prod
One can set up a post-commit hook as well... check out "The Book", for examples
of stuff.
Wouldn't be trivial, but I think that's how you'd do it, if you
weren't using a working
copy of some sort.
:D
On 6/21/07, Russ wrote:
> This is why we don't export, but check out a working copy for the prod
This is why we don't export, but check out a working copy for the production
environment. This way only modified file are pulled down when you do an
update. The only downside is that the code will take up roughly twice the
space.
You also got to make sure that .svn folders are protected. Apac
3 matches
Mail list logo
