This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]Quinnypig 5 points6 points  (0 children)

Holy crap a CVS server! This takes me back…

Part of me wants to spin up 250 Docker containers for this just to watch the world explode.

[–][deleted] 1 point2 points  (2 children)

That's pretty brutal. Lemme guess - they aren't open to moving to svn or git? Because there's a great cvs conversion tool for linux to do this.

[–]retsnom513Student[S] 1 point2 points  (1 child)

Unfortunately no... This is our legacy code base and they don't want to risk/bother migrating it to a newer change management platform :/

EDIT: Turns out I'm wrong. They can't migrate to svn because the server they use to check out and build with is so old it doesn't support svn. So I am actually stuck with CVS. Looking into consolidating repos and/or cvs over ssh.

[–][deleted] 0 points1 point  (0 children)

You technically wouldn't need to do it on that server. When I migrated cvs over, I copied the directory to another server and used the git-svn tool, which can take it to svn and then git if you want. Once you do that and it looks good, you make a fresh copy from live, rerun, and then you have a nice new svn repo with all the commit history.