#1
|
|||
|
|||
Protect Global Subroutines
As build master/software configuration manager for an International company, it's my responsibility to ensure the build scripts for all applications are secure and up to date. One problem we have is that several people use Visual Build to deploy files/applications due to it being an International company.
We have a sister team in Europe that uses the same development environment and support the same applications in production. Various people are responsible for deploying applications from the development server. This can cause a problem for everyone if one person makes a change to the global subroutines. Is there a way to protect them? Or better yet, allow someone to change them for their script but default back to the settings when they close the session of Visual Build... I do have all scripts stored in SourceSafe but it would be nice to protect the global subroutines. Thanks! |
|
|