RE: [viewvc-users] Using an Existing ViewVC mySQL db during SVN conversion

So does that mean I have to run 'update' after the 'rebuild' to get new updates by users into ViewVC db? If so, while running the 'Update' can users be logged on and committing there changes? When do I turn on the post-commit hook updates?


===============================================================
> c)If this is also not possible: Can the dev team start working on SVN 
> the repository as I run the 2 steps above?

Yes, with caveats.  'svndbadmin' can be run in parallel with other repository activity, and of course, Subversion is completely ignorant of ViewVC's database.  So your devs can do their Subversion work without this database population getting in the way.  Now, most admins configure their Subversion post-commit hook to run 'svndbadmin update REV' (so that ViewVC's MySQL database stays up-to-date as new revisions are committed).  If you plan to do the same, you'll probably want to comment out that bit of the hook while 'svndbadmin rebuild' does its initial population.
========================================================================

-----Original Message-----
From: C. Michael Pilato [mailto:[email protected]] 
Sent: Monday, October 25, 2010 5:42 PM
To: Pattalachinti, Ravi
Cc: [email protected]
Subject: Re: Using an Existing ViewVC mySQL db during SVN conversion

On 10/25/2010 05:14 PM, Pattalachinti, Ravi wrote:
> We are getting close to migrate the cvs data to svn.
> 
> The ViewVC conversion is adding 4 days in the downtime. Can you 
> recommend any suggestions?
> 
> In order for ViewVC to work with new SVN repository here is what I do: 
> 1)Python.exe svndbadmin rebuild “c:\repositories\SVN”
> 2)Python.exe svndbadmin update “c:\repositories\SVN”

[I'm assuming you are installing ViewVC 1.1.0 or better.]

Running 'svndbadmin rebuild' is essentially the same as running 'svndbadmin purge' + 'svndbadmin update'.  So unless there are new Subversion revisions being added to the repository while 'rebuild' is running, you needn't immediately follow that with an 'update'.

> Here are the questions:
> 
> a) We already did couple of trial conversions on our live data, and I 
> have the ViewVC database from our last trial. Our plan is to do a full 
> final conversion of cvs data to svn before closing the cvs repository.
> Can we use the existing ViewVC log database that was generated from 
> previous trial conversion or should I redo step 1 and 2 again after 
> final conversion?
>
> b)If not : Can I run only step 2 above to get only the new updates 
> since the last conversion?

That really depends on what cvs2svn does by way of conversion.  Let's say that your trial conversion resulted in N Subversion revisions.  If the first N revisions of your final cvs2svn run are identical to the N revisions created in your trial run, then yes, you should be able to just resume MySQL population from revision N+1.  If not, then you run the risk of the MySQL data being misaligned with the final repository data.

> c)If this is also not possible: Can the dev team start working on SVN 
> the repository as I run the 2 steps above?

Yes, with caveats.  'svndbadmin' can be run in parallel with other repository activity, and of course, Subversion is completely ignorant of ViewVC's database.  So your devs can do their Subversion work without this database population getting in the way.  Now, most admins configure their Subversion post-commit hook to run 'svndbadmin update REV' (so that ViewVC's MySQL database stays up-to-date as new revisions are committed).  If you plan to do the same, you'll probably want to comment out that bit of the hook while 'svndbadmin rebuild' does its initial population.

--
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2678205

To unsubscribe from this discussion, e-mail: [[email protected]].