On Jan 20, 2010, at 14:57, Hernan Castagnola wrote: > Is there any way (e.g editing the svn-properties) to make svn > give an Alert, or ask for confirmation when a sensitive file is updated. > I have been searching and I didn't find anything. > > Example > > Config.groovy is a sensitive file > > so on a Server X > > you set Config.groovy as a sensitive file > > when you run > > svn up and Config.groovy has been changed on the server, it tells you > > Config.groovy has been changed on ther server..... > Yes, No, Diff, etc > (as when you have a conflict) > > > I am asking this, because sometime files are committed by mistake. And maybe > is a good way to catch them before going to production.
No, there's nothing like that built-in, and I think you're trying to solve the wrong problem. It sounds like you are directly deploying your trunk to production with no testing, review or QA process; I would suggest that adding testing, review and/or QA would be the solution. For example, use a post-commit hook to send an email to the team with any changes as they get made. This way the team can review all changes, and hopefully spot incorrect ones before they become a problem. And instead of deploying direct from trunk, deploy from a tag. Presumably you have an individual who is responsible for deploying to production. This individual will test the trunk, and when satisfied, make a tag of it, and deploy the tag. There are post-commit scripts you can use to auto-deploy tags to production, so that the only step needed to deploy something is to make the tag in the repository. Now all you have to do is not create a tag when there is anything questionable or unverified going on in trunk.
