4

I'd like to set up a read-only Git repository mirroring our CVS repo (to allow easy history browsing with Gitweb). The mirror should ideally be updated in realtime. I've tried git-cvsimport but it takes about two minutes for an update run and probably puts high load on the CVS server.

What would you use for this job?

oliver
  • 81
  • 2

2 Answers2

1

Have you considered just switching to Git. I switched my team to Git from SVN over 6 months ago, and we haven't really missed SVN. Git is more flexible and powerful. It seems to have a bigger and more active community, and growing interest instead of declining interest Click here.

Anyhow the learning curve took us a few weeks, but now our development process and launch process are much quicker and happier.

We launch an internal web app ~10 times a day with a cherry-pick workflow that allows me to pick exactly which changes to launch. It also allows all the devs, myself included, to commit anything that is ready for review or launch at any time with little chance of merge conflicts. Most of which are whitespace changes.

Just something to chew on.

user35443
  • 6,309
  • 12
  • 52
  • 75
linuxdan
  • 4,476
  • 4
  • 30
  • 41
0

Like you say, a polling mechanism is too taxing for a CVS server.

The other solution would be to initiate that mechanism from the CVS server itself, through one of the CVS "commit support files" triggers.

From a commitinfo script, you could (if the CVS commit is validated by said script):

  • synchronize a CVS workspace (with a git repo inside) with the new content
  • run a program on that CVS workspace asking the git repo to add -A and commit.

That Git repo within a CVS workspace could be your read-only repo, or it could be an intermediate repo which would then, on each new Git commit, push all modification to said read-only Git repo.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250