Migrating from cvs to subversion is a fun way to spend your evenings. I'm trying to get a pre-commit check so that we can have path-based permissioning for specific users (or, ideally, groups). The subversion hooks are pretty flexible, but the example scripts are perl which is harder to install in my environment, and harder to modify since we don't perl...so I think I'll port the existing cvs commitinfo script - it doesn't do everything, but it works (in cvs land at least).
Then there's checking with JIRA at the same time - on some of our modules, you can only commit if you reference an open JIRA ion the commit log.
Then there's making fisheye complete its initial scan of the repository in less than geological time (ok, it's only been going for 2 weeks, is that enough time to evolve a better solution?).
In the end, when all else had failed, I read the manual, and found out that subversion does path-based authorisation in a pretty straightforward way, straight out of the box, using an Apache style authz file. As AP would say, you learn something every day...if you're not careful.
ReplyDelete