Question

We have a test engineer that does not need access to all of our firmware except the output .hex files. It would be nice to set him up with subversion so that he can Update and get the latest versions of our firmware and all that he would see on his end are the .hex files.
This would need to be for the entire repository on his end.
I know I can just limit his access to read-only, but we would like to take it a step further. I also know its not the best practice, but I’m just wondering if this is possible.
Thanks.

Answer 1

You don’t want him updating these files, but he can check them out? You can use a pre-commit trigger to do just that. I have one that allows you to restrict who can do what based upon file and directory names. These can be specified via glob (**/*.hex) or regular expression (/.*\.hex$/).

If you don’t want him to even be able to checkout any files but *.hex files, you’ll have some problems unless they’re all in the same directory.

Subversion lets you can specify directory access for read/write, but not individual file access. Thus, if your *.hex files are in a single directory tree, you could grant this user access to that tree only. But, if these are scattered throughout the repository, you’ll have a harder time.