We have the following code structure:
$
|-Core
| |- Project1
| |-CoreFile.cs
| |- Project2
| |- ...
|
|-NewProject
|- Project1
| |-CoreFile.cs
| |-NewFile.cs
|- Project2
|- ...
We have branched core into Project as a starting point and are adding files into NewProject solution's projects.
What we need to do now is set permissions on the Core code so that we can lock it down and stop people making changes to it. We are finding this difficult as TFS does not handle this situation very well.
Has anyone any suggestions as to best achieve this?
Step1: Navigate to the branch permission and press F12 to open the NetWork tool. Then you could select the network tab. Step2: Try to change the permssion. Step3: You could check the network record and get these parameters.
Go to Repository settings > Branch permissions. Click Add permission. In the Branches field, specify which branches the permission applies to, either by Branch name, Branch pattern, or Branching model.
Right-click the folder or file for which you want to set permissions, and then click Properties. In the Properties dialog box, click the Security tab. In the Add users and groups area, select Team Foundation Server Group to set permissions for a Team Foundation Server group. Otherwise, select Windows user or group.
With TFS, there are several ways that you can handle releases. You can tag/label each release branch or bug fix. But the relationship between release branches and the release is not always clear. Teams need to create a naming scheme and define a TFS branching strategy to help document the flow of change.
TFS does handle this and I am currently utilizing it in a scenario similar to yours. There is a permission called 'Check In' that you can set it 'Allow' or 'Deny' at user or group level. To be able to do this,
Note that in order to be able to change permissions, I believe you need to be an admin on server or project level. Also note that I am using TFS 2005.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With