On Wed, Jan 19, 2011 at 1:09 AM, Agnello George <agnello.dsouza at gmail.com> wrote: > HI > > i have currently started to deploy code into our production environment > from the the dev environment, we deploy code on to the production from the > svn , ( i do a svn export ) , some times not code is checked into the svn > and it does not throw me a error . > > is there a way i can verify or write a script to check each file that is in > the SVN is same as that in the dev environment . I'm something of a Subversion expert. (Years of professional work with it.) There is *no way* to force people to check in their code. That's one issue. The other is that you've discarded all the Subversion information when you use "svn export". Instead, maintain a working copy that you update or lock to a particular release, and do "rsync -avH --exclude=.svn --delete working-dir/ targetdir/ --dry-run". You can also use this command, without the "--dry-run" to actually publish the code from your working copy, and even integrate this as a "post-commit" for a working repository to be kept up-to-date at all times. I actually know people who do this for some development code, so the code publication is automatic when they submit code ot the trunk.