Record retention - need recommendations for deleting code reviews after x years
Our company is implementing record retention policies. This means after X years, code reviews must be deleted. Has anyone else faced this and if so, how are you handling it from both a process and technical perspective? We have a couple options we are discussing from a process standpoint, but I'm trying to figure out how we can technically do this with Collaborator.One option is x years from when a project was closed, go find and delete all the associated code reviews. Another option is x years from when an individual code review is completed (or created), delete the review. We are using Collaborator, which stores data in both the SQL database and in flat files on the server that have hash names. How can you delete a code review (no button to delete a completed review)? Will this delete the hash file? If not, how in the world do you locate the associated hash files (I know the path they are in, but with the hash names no idea how to tell what is what)? I look forward to any information that can be shared or recommended on this.
specifying script library path with a URI
Good afternoon, we are trying to figure out the Script Library path designator. Does the library have to be in a directory that is accessed only through the file syste or is it possible to access a library that is available through a URI for the library? While it is possible to access the library in the second way, it would be more consistent with our development environment to access the library through a URL. We are trying to eliminate the need for a shared drive in our developement, testing and integration environment. v/r, Ed Lorden Software Tester