Agnello George
2011-Jan-19 06:09 UTC
[CentOS] not able to check in all code into svn which creates problem in deployment
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 . -- Regards Agnello D'souza -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110119/27c73167/attachment-0002.html>
John Doe
2011-Jan-19 09:53 UTC
[CentOS] not able to check in all code into svn which creates problem in deployment
From: Agnello George <agnello.dsouza at gmail.com>>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 .Maybe you should ask on the svn mailing list... But if you do an 'svn diff' in dev, it should compare dev to what is in the repo... no? JD
Kai Schaetzl
2011-Jan-19 10:02 UTC
[CentOS] not able to check in all code into svn which creates problem in deployment
You should better ask this on an SVN list. Thanks. Kai -- Get your web at Conactive Internet Services: http://www.conactive.com
Hakan Koseoglu
2011-Jan-19 10:10 UTC
[CentOS] not able to check in all code into svn which creates problem in deployment
On 19 January 2011 06:09, Agnello George <agnello.dsouza at gmail.com> wrote:> 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 .find . -type f | grep -v .svn | xargs md5sum then diff the output from each server. -- Hakan (m1fcj) - http://www.hititgunesi.org
Les Mikesell
2011-Jan-19 14:12 UTC
[CentOS] not able to check in all code into svn which creates problem in deployment
On Wed, Jan 19, 2011 at 12:09 AM, Agnello George <agnello.dsouza at gmail.com> wrote:> 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 . >You should design a process where the only way to get things to work is to go through svn. That is, check in from the dev location(s), check out in a staging/test environment where you build and test but never edit anything, then push to production. And in general, I'd prefer an 'rsync -C' from the staging checkout to an export from the svn server - that lets you do an 'rsync -Cn' to verify that the contents are identical between staging and production and an 'svn status' or 'svn diff' to check staging against the repository. And if something isn't checked in, it basically doesn't exist. -- Les Mikesell lesmikesell at gmail.com
Nico Kadel-Garcia
2011-Jan-20 04:30 UTC
[CentOS] not able to check in all code into svn which creates problem in deployment
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.
Reasonably Related Threads
- error --- > any idea ?? Kernel: Additional sense: Invalid command operation code
- how to access external USB drive in single user mode
- unable to check in code to svn when files contain spaces or characters
- how to check the number of thread on apache server
- display issue after installing centos 5.5 on hp probook 4420s