TFS installation and management

ArticleDirectory

• 2.3.1. Permission description
• 2.3.2. Configure project Permissions
• 2.3.3. Report Service permission Configuration
• 2.3.4. portal website permission Configuration
• 3.2.1. Field Definition
• 3.2.2. layout Modification
• 3.2.3. workflow Modification

After a few days of TFS, I will write down the configuration and installation points, hoping to help you. This article focuses on installation and configuration. The next article will introduce how to use and usage.

The content of this article is brief:

 

1. installation and deployment 1.1. Process

 

1.2. Install the Operating System

2 GB or above memory and GB hard disk space are recommended for the server.

It must be Windows 2003 or windows.

1.3. Configure the Operating System

Change the computer name.

Install IIS.

Users who create TFs to run the report service and automatically build the service are recommended to belong to the Administrators group. The recommended name is:

Tfsbuilder is used to automatically build services.

Tfsreports: used for the report service.

1.4 install necessary software

Install Visual Studio 2010.

For SQL Server 2008, you must install the report service.

Install SharePoint 3.0 (installed automatically during TFs installation ).

1.5. Install TFs

The installation of tfs2010 adopts a simple automatic wizard. Basically, the default configuration can be installed. Pay attention to the associated configuration of SharePoint and report service.

1.6. Precautions

The name of the server must be modified before TFs is installed. Otherwise, if you modify the computer name after the installation, several TFs services cannot run properly.

If the report service and SharePoint are not properly installed before TFs is installed, TFS will not automatically configure the association of these services. Manual configuration will be complicated and the success rate will be low.

Install vs2010 on the server to use its client for configuration after TFs installation, and have the highest permissions.

It may take 3 to 5 hours for the server to start from bare metal to install TFs.

2. TFs management 2.1. Project Structure

TFS has a concept called Project set for project management, that is, you can create a set, which can create related projects.

 

Application scenarios:

1. An enterprise can create a project set based on each project group. Each project group has its own project set.

2. A large project contains several small project management methods.

2.2. Create and delete a project

Open the team manager of vs2010 and right-click the project set to operate.

 

Enter the project name, whether to create a portal, and whether to use the newSource codeManager and so on. Finally, TFS will automatically help you create the project you set.

To delete project management, open the vs2010 team resource manager, right-click the project, and choose:

 

Note: The deleted project information does not automatically delete the portal. You need to manually delete it. For the deletion method, see the subsequent sections.

2.3. Permission configuration 2.3.1. Permission description 2.3.1.1. Permission Association

TFS permissions are associated with operating system users or domains. TFs supports permission management for database accounts, operating system accounts, and domain accounts. Generally, TFS is used for less than 20 users. It is recommended that you directly use the operating system account for convenience and simplicity. If there are more than 20 teams, we recommend that you use the method associated with the domain account.

2.3.1.2. TFs permission structure

The permission structure of TFS is hierarchical based on the project set, project, and content. The lower layer can overwrite the upper-layer permission configuration.

 

2.3.1.3. Permission Group

TFS has a default group in each permission layer. You can modify existing groups or create your own groups.

Under a project set, the default settings are as follows:

 

Under each project, the default settings are as follows:

 

Each permission group can contain different members and has different operation permissions.

2.3.2. Configure project Permissions

Project permission configuration includes project-level and SourceCode, Region, Team query, and generated permission control.

Project-level permission control is only used to control the user's access permissions to the project. The same applies to the project set. If you have project-level access permissions, you do not have source code, region, and other permissions. You need to configure them one by one. However, TFS generates four permission groups by default, and default configurations are available for different content, generally, you only need to configure the members of these groups.

To adapt to the default permission group, add a member as an example:

Click the vs2010 Team Project Manager, right-click the Team Project, and perform the following operations:

 

The following dialog box is displayed. Select a participant and click Properties:

 

In the following dialog box, select a Windows user or group, and enter the user name created in the system in the new dialog box.

Note: For simple configuration, create an account for all users involved in TFs management in the operating system, and then each user will use the user name/password of the current operating system as the credential for logging on to TFs.

 

After the operation is complete, the configured user can normally access TFs and perform relevant work. The default four groups have different permissions. For example, the visitor has the least permissions, the user in the current group has the least permissions, and the Administrator group has the highest permissions.

When a user belongs to both the Administrator group and the Access Group, the current user has all the permissions of the Administrator and the visitor.

If you need to assign detailed permissions, you can create your own user groups for management. However, the newly created user group must be assigned permissions at the source code, region, Team query, and generation levels, and then be added to its members.

Source code permission, which can be divided by directory permissions.

Region permissions are mainly used to control work items, such as whether a work item can be created or whether a task can be disabled.

The team query mainly controls the permissions of custom query information.

Generate, mainly to control the permissions of the generate operation.

2.3.3. Report Service permission Configuration

The permissions of the report service are independent of those of the TFS project management permissions. The settings are as follows:

Open the report Configuration Manager, select the report manager URL tab, and click its URL to go to the following website:

 

Click tfsreports to enter the subdirectory. Select the project set you want to Configure permissions for, and then select the project to enter the subdirectory.

 

Click the following attribute:

 

Click security and then create a role assignment,

 

The following page is displayed:

 

You must enter the group name or user name in the current operating system for the group or user name. Select the permission content based on the actual situation and click OK to submit the operation.

2.3.4. portal website permission Configuration

The permissions of the TFS portal are independent of those of the TFS project. The setting method is as follows:

In the vs2010 team resource management of the server, select a project under the project set, right-click the project portal, and the following site appears:

 

Click the link in the red circle-website operations. In the drop-down box, select website settings. The page is displayed.

 

Select people and groups. The page is displayed.

 

Click Create to display the new user page.

 

User/user group. You must enter the user or group in the operating system. After Entering the user or group, you can click the check name to confirm. Select the permission based on the actual situation, and click OK to complete the operation.

2.4. Manage work items

Once a work item is created in TFs, it cannot be deleted. The main consideration should be that Microsoft believes that there must be a plan to add work items, and modifications can be provided, but the UI page will not be deleted. If you want to delete a work item, you can use the command line method to delete it. The procedure is as follows:

Enter the command line mode,

 

Enter the following command:

 

Collectionname: name of the project set, which must contain HTTP and port.

Idnum: ID number to be deleted.

3. template customization 3.1. Method

TFS supports customization of work items and process templates. Microsoft team Foundation server 2010 power tools is recommended. After installation, you can directly export the template definition file from the server. After saving the file, it is directly imported to the TFS server. If you do not use the tool, you can use the command line method (not recommended ).

After Microsoft team Foundation server 2010 power tools is installed, this function is added to:

 

3.2. Work Item

You can customize work items, such as bugs and tasks, or create a work item. This document describes how to modify the default task work item.

To use Microsoft team Foundation server 2010 power tools, perform the following operations:

 

The Select Type dialog box is displayed. After selecting a project set, project, and type, the page is displayed:

 

Fields is a field that defines the task work item.

Layout is the field layout that defines the pop-up dialog box for creating work items.

Workflow is a workflow that defines the State Changes and operations of a work item.

3.2.1. Field Definition

A new field definition can be added to the template. The field information can be referenced by a tool:

 

 

Select the custom definition to be added from work item field explorer as needed.

3.2.2. layout Modification

 

The template can define the position of fields in the window, and you can use the preview function to check.

Create a new control at the specified position, and select filedname and type in the Properties window,

 

Here you can select the new type or existing type you just imported in the previous step. Type specifies the control type, which can be a drop-down box, date selection, text, and so on.

3.2.3. workflow Modification

The template also allows you to customize workflows. You can modify the templates by using the vs designer and the control of the Toolbox.

3.3. Field ing

After TFs is exported to the project file, you can customize the ing between TFs fields and peoject fields as follows:

Download the ing file:

 

Project set name and project name can be customized based on actual conditions.

After the download is complete, open the XML in the editor,

 

You can add a record, corresponding to the field attribute in the work item field explorer, and the field in the project.

After the modification is completed, use the command to upload the file to TFs: