This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Protium Software Page 4 of 66 http://protiumsoftware.com
1.0 Introduction
This guide describes how to administer Code Review Tool application. It explains how to install,
upgrade and uninstall Code Review Tool application. It also explains how to configure your
Code Review Tool installation.
2.0 Installation Scenarios
CodeReviewTool application can be installed in following ways:
Installation Type Details
Single Server Installation
In this scenario you have a single Windows Server with both IIS and SQL Server installed on it and you choose to install Code Review Tool on this server.
Separate Database and Web Application Installation
In this scenario you have two different Windows Servers with one server running IIS and other running SQL Server. You first install Code Review Tool database on the SQL Server. You then install Code Review Tool Web Application on IIS 7.0 Server and specify the Code Review Tool database server details for Web Application to connect to Code Review Tool database.
3.0 Installing
3.1 Pre-requisites
To install Code Review Tool Database you need the following:
1. SQL Server 2008 (or above) installed with File Streams and Full-Text Indexing support
2. You need Administrator privileges on the machine
3. You need Administrator privileges on the SQL Server instance
To install Code Review Tool Web Application you need the following:
1. Windows Server 2003 (or above) or Windows Vista SP2 (or above) or Windows 7
2. IIS 7.0 (or above)
3. You need Administrator privileges on the machine
Protium Software Page 7 of 66 http://protiumsoftware.com
3.3.3 Setup Type Step
This step provides you with following setup options:
Option Details
Install Database This option allows you to install Code Review Tool Database alone on a SQL Server.
Install Web Application and Activate Product
This option allows you to install Code Review Tool Web Application on a Windows Server with IIS 7.0. This also allows you to activate your installation with a product key.
Active Product This option allows you to activate your Code Review Tool installation alone with a product key.
Install Database, Web Application and Activate Product
This option allows you to install both Code Review Tool Database and Web Application on a single Windows Server with IIS and SQL Server. It also allows you to activate your Code Review Tool product with a product key.
Protium Software Page 12 of 66 http://protiumsoftware.com
3.3.8 Database File Locations Step
This step collects following input for Code Review Tool database:
Input Details
Database Log Directory
The directory for Code Review Tool database log files. In large installation scenarios, for performance, it is generally better to specify a directory for log files which is different from database directory.
Full Text Database Directory
The directory for full text database files needed for search feature.
File Streams Directory
The directory for file streams of Code Review Tool database.
Protium Software Page 18 of 66 http://protiumsoftware.com
3.3.14 Web Application Step
This step collects following inputs for Code Review Tool web application:
Input Details
Application Name
The “virtual directory name” under Web Site for the Code Review Tool Web application. The default “/” works if you are creating a new web site for Code Review Tool Web application. If you are using an existing web site sharing it with other web applications, then you might want to specify a different virtual directory other than “/”.
Application Directory
The physical directory under which the Code Review Tool web application resides. This is generally the same as “Site Directory” in previous step if you are creating a new site for Code Review Tool application otherwise you specify a different physical directory other than “Site Directory”.
Protium Software Page 25 of 66 http://protiumsoftware.com
7. AddressBook More information on certificate stores can be found at http://msdn.microsoft.com/en-us/library/system.security.cryptography.x509certificates.storename.aspx
Only one of “Certificate Name” or “Certificate Hash” values needs to be specified.
3.3.21 Web Application Upload Directory Step
This step allows you to specify a directory where the Code Review Tool web application
downloads and stores change sets temporarily while creating reviews from different version
Protium Software Page 27 of 66 http://protiumsoftware.com
3.3.23 Web Application User Accounts Step
This step allows you to select one of the following Code Review Tool user accounts types:
Type Details
ASP.NET SQL User Accounts
This allows Code Review Application to integrate with ASP.NET SQL user authentication. The user accounts are kept in the Code Review Application database.
Windows Domain User Accounts
This allows Code Review Application to integrate with your existing Active Directory or LDAP installation to authenticate users.
Windows Local Machine User Accounts
This allows Code Review Application to integrate with local user accounts on a Windows machine to authenticate users.
Protium Software Page 31 of 66 http://protiumsoftware.com
3.3.27 Web Application Roles Step
This step allows you to specify the role names for Code Review Tool users and administrators:
Type Details
User Role Name
All regular Code Review Tool users should be present in this role to log into Code Review Tool web application.
Admin Role Name
All administrator users of code review tool should be present in this role to access administrator specific features of Code Review Tool web application. Users belonging to administrator role have the following specific features:
1. Administrator can view and manage reviews across all the users of the Code Review Tool
2. Administrator can notify all the users with an email using “Notify Users” link from “Accounts” page.
Protium Software Page 34 of 66 http://protiumsoftware.com
3.3.30 Protect Configuration Step
This step allows you to select one of the following for protecting various configuration files:
Type Details
Encrypt Configuration Files
Select this if you would like to encrypt sensitive information in configuration files like web.config, craconfig.exe.config etc. For production deployments, we recommend you choose this setting to keep your installation secure.
Don’t Encrypt Configuration Files
Select this if you would like to don’t want to encrypt sensitive information in configuration files like web.config, craconfig.exe.config etc. This option is only useful for scenarios where you want edit the configuration settings manually to handle scenarios which are not supported by setup. NOTE: You can encrypt the files after edit them as describe in section “8.8.2 Encrypting Code Review Tool sections in web.config”
Protium Software Page 35 of 66 http://protiumsoftware.com
3.3.31 Product Activation Step
This step allows you specify various inputs for activating your Code Review Tool application
after installation using a valid product key.
Input Details
Product Key Product key for Code Review Tool application. This product key is 35 characters wide with a ‘-‘ character after every 5 characters. For e.g. ABCDE-FGHIJ-KLMNO-PQRST-UVWXY-Z1234
Activation Server URL
Product Activation Server URL. This should be http://codereviewtool.com.
Protium Software Page 45 of 66 http://protiumsoftware.com
This section is physically stored in “bin\CodeReviewApplication.config” file and multiple
different configuration files, for e.g. web.config, craconfig.exe.config, crutil.exe.config etc.
share it.
Element Name Purpose
CoreConfig Contains core configuration settings for Code Review Tool application.
SearchConfig Contains search configuration settings for Code Review Tool application.
UIConfig Contains Web UI configuration settings for Code Review Tool application.
SourceControlManagers Contains configuration about different Source Control Manager plug-ins used by Code Review Tool application.
Depots Contains configuration about different global depots, in different Source Control Managers, used by Code Review Tool application.
TextFiles Contains a list of file extensions which need to be treated as text files by Code Review Tool diff engine while computing differences between two versions of the file with specified extensions.
CodeFormatters Contains a list of file extensions associated with different code formatters for syntax highlighting of source code.
Languages Contains definitions of different languages used by generic code formatter for syntax highlighting of source code.
8.1.1 CoreConfig Element
This element contains the following core configuration settings for Code Review Tool
application.
Name FilesRootFolder
Type String
Required Yes
Default Value
“upload”
Description Specifies either relative of absolute path to folder which is used to store temporarily downloaded change lists from version control systems while creating reviews.
Protium Software Page 46 of 66 http://protiumsoftware.com
Default Value
“bin\crt.exe”
Description Specifies either relative of full path to “crt.exe” which is used to compute differences between two versions of a file while creating reviews.
Name ReviewStatusChangeEmail
Type Boolean
Required No
Default Value
false
Description A flag indicating whether to send review status change email notifications or not.
Name Registration
Type Boolean
Required No
Default Value
false
Description A flag indicating whether to allow free new user registration through “Register” link from login page.
Name RegistrationRequest
Type Boolean
Required No
Default Value
false
Description A flag indicating whether new user registrations should be treated as requests or not. If “false” the user is allowed to register directly using “Register” link. If “true” the registration requests from users are queued and administrator approves or rejects each request. When admin approves a request email notification is sent to email specified in the request with a unique link associated with the request so that the user can complete the registration using the unique link. NOTE: This property value is applicable only when “Registration” property has a value of “true”.
Protium Software Page 47 of 66 http://protiumsoftware.com
Description Specifies the email ID to which the feedback is sent when a user submits a feedback using “Feedback” link.
Name SqlCommandTimeout
Type Int
Required No
Default Value
120
Description Specifies time out for database commands in seconds.
Name SyntaxHighlighting
Type Boolean
Required No
Default Value
true
Description A flag indicating whether to enable or disable syntax highlighting.
Name UseRemoteScripts
Type Boolean
Required No
Default Value
false
Description A flag indicating whether to use jquery scripts and stylesheets from well known remote content distribution network (https://ajax.googleapis.com) or not while rendering web pages. If false, the local copy of the jquery scripts and stylesheets installed with the application are used while rendering web pages.
Name UserRole
Type String
Required Yes
Default Value
CRUsers
Description Role name, or Group name, for regular Code Review Tool users. All Code Review Tool users should belong to this group.
This element contains the following Web UI configuration settings for Code Review Tool
application:
Name DiffViewType
Type Enumeration (“Merged”, “SideBySide”)
Required No
Default Value
“Merged”
Description Specifies the default diff view that should be used to render differences when user wants to view differences between two versions of a file.
Name SummaryDiff
Type Boolean
Required No
Default Value
true
Description A flag indicating whether to enable summary differences view or not. In summary differences view similar sections between two versions of a file are summarized in a short summary section to allow users to focus on differences.
Protium Software Page 50 of 66 http://protiumsoftware.com
Required No
Default Value
3
Description Specifies the number of similar lines to show before and after summary section in differences view between two files. NOTE: This value is only used if “SummaryDiff” value is “true”.
Name SourcePreviewExtraLines
Type Int
Required true
Default Value
5
Description Specifies the number of similar lines to show before and after the range of source lines associated with a comment thread in comment thread details view.
Name AllowPackageUploads
Type Boolean
Required true
Default Value
false
Description A flag indicating whether diff packages can be uploaded to an existing or new review. NOTE: This property is not supported currently and its value should always be “false”.
An example of UIConfig element is:
<UIConfig
DiffViewType="Merged"
SummaryDiff="true"
SummaryContextLines="3"
SourcePreviewExtraLines="5"
AllowPackageUploads="false"/>
8. 1.4 SourceControlManagers Element
This element contains configuration about different Source Control Manager plug-ins used by
Code Review Tool application in a collection of “SourceControlManager” elements.
Each “SourceControlManager” element contains the following properties
Protium Software Page 51 of 66 http://protiumsoftware.com
Name Name
Type String
Required Yes
Description Specifies a unique name for the source control manager plug-in which is used to identify the plug-in from “depot” section subsequently.
Name Type
Type String
Required Yes
Description Specifies the type information, in the standard Type format, for loading the source control manager plug-in assembly which implements the “ISourceControlManager” and “ISourceControlManagerSetup” interface.
Name Path
Type String
Required No
Description Specifies the relative or full path to the source control manager plug-in assembly. If the paths are relative they should be with the “web application” folder path, which by default is “%systemdrive%\inetpub\wwwroot\CodeReviewTool”.
Each Source Control Manager plug-in specific settings can be different. The schema for these
settings is described in “Settings” element in the following format:
Item Description
Element name Name of the setting for Source Control Manager
Element content Description for the setting to use in UI for Source Control Manager
“required” property
Boolean property indicating whether the setting is optional or required
“password” property
Boolean property indicating whether the setting is part of credential or not. Credential settings are shown to the user with “masked” character like “*”.
For e.g. the Team Foundation Server plug-in specifies the following schema for its depot
This element contains configuration about different global depots, for different Source Control
Managers, used by Code Review Tool application in a collection of “Depot” elements.
Each “Depot” element contains the following properties
Name Name
Type String
Required Yes
Description Specifies a unique name for the depot of a particular source control manager which is used to identify the depot subsequently.
Name Type
Type String
Required Yes
Description Specifies the name of the Source Control Manager plug-in which is used to represent the type of the depot. This value should be listed in a “SourceControlManager” element under “SourceControlManagers” element.
Each “Depot” element contains a “Settings” element listing different settings for the depot in
the format as dictated by the settings schema in the related “SourceControlManager” element.
For e.g. the following is an example of an instance of TFS depot:
Protium Software Page 53 of 66 http://protiumsoftware.com
Server=https://tfs.codeplex.com/tfs/TFS24
ProjectName="testproject"
UserName="test-user"
Password="user!password789"
Domain="domainname" /> </Depot>
NOTE: The properties in “Depot/Settings” element should match the schema for the settings as
described in related “SourceControlManager/Settings” element.
8. 1.6 TextFiles Element
This element contains a list of file extensions which need to be treated as text files by Code
Review Tool diff engine while computing differences between two versions of the file with
specified extensions in a collection of “TextFile” elements.
Each “TextFile” element contains the following properties
Name Extension
Type String
Required Yes
Description Specifies the file name extension which is to be treated as text file while computing differences between two versions of files with the specified extension. Generally source control manager helps in the identification of whether a file is text file or not. This section is useful for scenarios when a file type gets wrongly interpreted as binary file by Code Review Tool and no differences are displayed for that particular file type. In this scenario using this section you can override the file type to be interpreted as text file by Code Review Tool to compute and display the differences correctly.
Protium Software Page 54 of 66 http://protiumsoftware.com
This element contains a list of file extensions associated with different code formatters for
syntax highlighting of source code in a collection of “CodeFormatter” elements.
Each “CodeFormatter” element contains the following properties
Name Extension
Type String
Required Yes
Description Specifies a unique file extension value of source code for which the formatter should be used.
Name Formatter
Type String
Required Yes
Description Specifies the name of “CodeFormatter” which can either be a name of generic code formatter or that of a specific code formatter.
There are two types of code formatters:
Code Formatter Type
Description
Generic Code Formatter
This code formatter is a generic formatter which uses a “Languages/Language” element to format the source code for a particular language. Following is the list of generic code formatters specified by default in “web.config”:
1. ruby 2. python 3. perl 4. java
Specific Code Formatter
These code formatters are implemented and supported by Code Review Tool by default to support formatting a single language source code. Following is the list of specific code formatters:
1. cpp 2. xml 3. c# 4. css 5. html 6. javascript 7. php 8. sql 9. asax 10. ashx
Protium Software Page 55 of 66 http://protiumsoftware.com
11. aspx 12. vb.net
Some examples of “CodeFormatter” elements for different languages are listed below:
<CodeFormatters>
<CodeFormatter Extension=".cpp" Formatter="cpp"/>
<CodeFormatter Extension=".h" Formatter="cpp"/>
<CodeFormatter Extension=".hpp" Formatter="cpp"/>
<CodeFormatter Extension=".cs" Formatter="c#"/>
<CodeFormatter Extension=".css" Formatter="css"/>
</CodeFormatters>
8. 1.8 Languages Element
This element contains definitions of different languages used by generic code formatter for
syntax highlighting of source code in a collection of “Language” elements.
Each “Language” element describes the language properties to be used by the generic code
formatter described in previous section.
Each “Language” element contains the following properties:
Name Id
Type String
Required Yes
Description Specifies a unique name for the language element which is used by generic code formatter to lookup language details to perform syntax highlighting of source code.
Name Keywords
Type String (in element content)
Required Yes
Description Describes the keywords for the language separated by space.
Name SingleLineCommentRegEx
Type String
Required No
Description Specifies the .Net regular expression used to identify a single line comment for the language.
<Keywords>abstract continue for new switch assert default
goto package synchronized boolean do if private this break
double implements protected throw byte else import public
throws case enum instanceof return transient catch extends
int short try char final interface static void class
finally long strictfp volatile const float native super
while</Keywords>
</Language>
8.2 system.net/mailSettings/smtp Section
This section is used to configure SMTP settings for sending review status change email notifications to Code Review Tool users. More details at http://msdn.microsoft.com/en-US/library/ms164240(v=VS.80).aspx. An example “smtp” element is: <system.net>
Protium Software Page 58 of 66 http://protiumsoftware.com
8.4 authentication Section
This section is used to configure the authentication scheme for Code Review Tool. More details at http://msdn.microsoft.com/en-us/library/532aee0e(v=VS.80).aspx.
8.5 membership Section
This section is used for managing and authentication of user accounts for Code Review Tool. This section is physically stored in “bin\Membership.config” file and multiple different
configuration files, for e.g. web.config, craconfig.exe.config etc. share it.
More details at http://msdn.microsoft.com/en-US/library/1b9hw62f(v=VS.80).aspx.
8.6 roleManager Section
This section is used to configure role management for Code Review Tool. This section is physically stored in “bin\RoleManager.config” file and multiple different
configuration files, for e.g. web.config, craconfig.exe.config etc. share it.
More details at http://msdn.microsoft.com/en-US/library/ms164660(v=VS.80).aspx.
8.7 trace Section
This section is used to configure diagnostic tracing for Code Review Tool. More details at http://msdn.microsoft.com/en-US/library/6915t83k(v=VS.80).aspx. Code Review Tool writes a diagnostic trace with error details in “Trace.log” file in the Code Review Tool application folder. By default this file is located at “%systemdrive%\inetpub\wwwroot\CodeReviewTool\Trace.log”.
The sections are encrypted using a key container named “CodeReviewApplicationKeys”. This key container contents are unique on each machine and contains the keys necessary for encrypting and decrypting relevant sections. http://msdn.microsoft.com/en-us/library/dtkwfdky(v=VS.90).aspx provides a step by step example of how to encrypt and decrypt “web.config” sections. http://msdn.microsoft.com/en-us/library/53tyfkaw(v=VS.90).aspx contains more details on encrypting protected configuration in “web.config” sections.
8.8.1 Decrypting Code Review Tool sections in web.config
The following is a sample script to decrypt relevant sections of Code Review Tool in web.config file assuming you have installed Code Review Tool to “%systemdrive%\inetpub\wwwroot\CodeReviewTool” folder:
1. set path=%path%;%windir%\Microsoft.NET\Framework\v2.0.50727;
2. cd /d %systemdrive%\inetpub\wwwroot\CodeReviewTool
8.8.2 Encrypting Code Review Tool sections in web.config
The following is a sample script to encrypt relevant sections of Code Review Tool in web.config file assuming you have installed Code Review Tool to “%systemdrive%\inetpub\wwwroot\CodeReviewTool” folder:
1. set path=%path%;%windir%\Microsoft.NET\Framework\v2.0.50727;
2. cd /d %systemdrive%\inetpub\wwwroot\CodeReviewTool
9.0 Client Installation and Upgrade If you would like to install Code Review Tool on other machines to use client tools, like craconfig.exe and crutil.exe for pre-commit reviews or integration purposes, you can use “craconfig.exe –client” commands. For installing client tools use the following command: c:\ > craconfig.exe -client -install -dir {client install directory} [-sourcedir {source directory name} (C:\temp\download\bin)] “-dir” is the directory to install Code Review Tool client tools. “-sourcedir” is an optional argument specifying the source of installation, which by default is the downloaded and extracted location of Code Review Tool distribution zip file. For updating client tools use the following command: c:\ > craconfig.exe -client -upgrade -dir {client install directory} [-sourcedir {source directory name} (C:\temp\download\bin)] “-dir” is the installed directory of Code Review Tool client tools which needs to be upgraded. “-sourcedir” is an optional argument specifying the source of installation, which by default is the downloaded and extracted location of Code Review Tool distribution zip file.
10.0 Automatic Review Creation for Team Foundation System Check-ins This section explains how to automatically create reviews for change sets as they are checked into Team Foundation System version control. http://msdn.microsoft.com/en-us/magazine/cc507647.aspx contains more details about TFS notifications. The binaries which are required for achieving this integration are:
Binary Name Purpose
Bissubscribe.exe A binary shipped with Team Foundation Server distribution. This binary is needed to register an event sink for Check-in notifications. This binary is generally present in “c:\Program Files\Microsoft Team Foundation Server 2010\Tools” folder.
Protium Software Page 61 of 66 http://protiumsoftware.com
TfsNotifier.exe A binary, which is hosted as Windows Service, to process the TFS Check-in notifications. This binary is shipped with Code Review Tool distribution. This binary receives the TFS Check-in notifications on SOAP and then does the necessary processing to create the review and start it automatically on behalf of change set committer. This binary is present in folder where the Code Review Tool client is installed. To install Code Review Tool client binaries see the above “9.0 Client Installation and Upgrade” section.
Steps to enable automatic review creation for TFS:
1) Install or upgrade your Code Review Tool installation to latest binaries a. To install Code Review Tool follow “3.0 Installing” section b. To upgrade Code Review Tool follow “6.0 Upgrading” section
2) Install or upgrade Code Review Tool client binaries on Code Review Tool machine. a. You can use “C:\Program Files\Protium Software\CodeReviewTool” as the
client installation folder. b. To install or upgrade Code Review Tool client binaries follow instructions
specified in “9.0 Client Installation and Upgrade” section. 3) Install TfsNotifier.exe service on Code Review Tool machine from client binaries folder
using “installutil.exe” a. C:\>%windir%\microsoft.net\framework\v2.0.50727\installutil.exe
“C:\Program Files\Protium Software\CodeReviewTool\TfsNotifier.exe” b. During service installation, when prompted for service account credentials use
an account which has read permissions for your TFS collection. c. Configure TfsNotifier settings by following “10.1 Configuring TfsNotifier” section
below. 4) On Team Foundation Server machine register the TfsNotifier service end point as
listener for Check-in notification using “Bissubscribe.exe” a. C:\>"c:\Program Files\Microsoft Team Foundation Server
b. Configure your networking firewall on Team Foundation Server and Code Review Tool machine to allow check-in notifications to be sent and received on the port you specified above for “/address” argument.
5) On Code Review Tool machine start the TfsNotifier service a. C:\>Net start TfsNotifier
6) Check-in in a dummy change to TFS project configured in TfsNotifier to see if the review gets created automatically or not.
a. NOTE: TFS uses batch job to send check-in notifications every 2 minutes. So sometimes it can take more than 2 minutes for a review to be created after a change set is checked in.
Protium Software Page 62 of 66 http://protiumsoftware.com
b. If the review is not getting created automatically check for failure details in Application event log from “TfsNotifier” source using Eventvwr.exe.
c. http://blogs.msdn.com/b/granth/archive/2009/10/28/tfs2010-diagnosing-email-and-soap-subscription-failures.aspx contains more details about how to debug TFS SOAP notifications.
10.1 Configuring TfsNotifier
You can configure TfsNotifier behavior by editing TfsNotifier.exe.config file. This file is generally present in your client installation folder e.g. “C:\Program Files\Protium Software\CodeReviewTool\TfsNotifier.exe.config”.
10.1.1 Services Configuration Section
This section configures the listening end point for TfsNotifier service.
You can configure the listening end point (port) for TfsNotifier using “baseAddress” attribute specified in system.serviceModel/services/service/host/baseAddresses/add element. NOTE: The listening port value specified above should be configured in networking firewall to allow notification traffic.
10.1.2 Plugins Configuration Section
This section specifies the source control plug-ins and the depots. You only need to configure the <Depot/> entries for your scenario. <Depots>
Generally there is only one depot configured. If want to use a single TfsNotifier to create reviews for different Team Foundation Server collections you can have more Team Foundation Server depots configured in the Plugins section. Each “Depot” element contains the following attributes:
Name Name
Type String
Required Yes
Description Specifies a unique friendly name for the TFS depot to be referred later elsewhere in the configuration file. For e.g. “tfs”.
Name Type
Type String
Required Yes
Description Don’t edit this. Specifies the type of the source control manager. This should be “TeamFoundation”.
The “Depot/Settings” element contains the following attributes:
Name Server
Type String
Required Yes
Description Specifies the TFS server URL for the project. For e.g. http://localhost:8080/tfs
Name ProjectName
Type String
Required Yes
Description Specifies the TFS project name. For e.g. “Testing”
Name UserName
Type String
Required No
Description Specifies the account’s user name for accessing the TFS project.
Protium Software Page 64 of 66 http://protiumsoftware.com
Name Password
Type String
Required No
Description Specifies the account’s password for accessing the TFS project
Name Domain
Type String
Required No
Description Specifies the account’s domain name for access the TFS project if the account is in a domain.
NOTE: If you have configured TfsNotifier.exe service to run in an account with access to your TFS projects then you don’t have to specify UserName, Password and Domain optional attributes in <Depot/Settings/> element.
10.1.3 TfsNotifier Configuration Section
This section configures Code Review Tool server on which the reviews should automatically created for different TFS projects. This section also configures which reviewers should be invited for change sets committed by a particular user in TFS project. <TfsNotifier TraceLogFile=" "> <CodeReviewServers> <CodeReviewServer Url="http://your-codereviewtool-site.com" UserName="" Password="" Depots="tfs"> <Committers> <Committer Name="domain\username1" Author="codereview-username1" Reviewers="codereview-username1,codereview-username2"/> <Committer Name="domain\username2" Author="codereview-username2" Reviewers="codereview-username1,codereview-username2"/> </Committers> </CodeReviewServer>
</CodeReviewServers> </TfsNotifier>
TfsNotifier element contains the following sub-elements:
Item Description
CodeReviewServers Collection of CodeReviewServer elements.
CodeReviewServer Describes the settings for a Code Review Tool server for creating reviews.
CodeReviewServer/Committers Collection of Committer elements.
CodeReviewServer/Committers/Committer Describes the details for creating review for each user who commits a change set.
Protium Software Page 65 of 66 http://protiumsoftware.com
TfsNotifier element contains the following attributes:
Name TraceLogFile
Type String
Required No
Description Specifies a file name for logging TfsNotifier detailed trace messages. If not specified not trace log is generated. The trace log can be used to debug notification processing issues.
CodeReviewServer element contains the following attributes:
Name Url
Type String
Required Yes
Description Specifies a URL for your Code Review Tool server on which reviews should be created automatically. For e.g. http://yourcodereviewtoolserver
Name UserName
Type String
Required No
Description Specifies the “administrator” user name for the Code Review Tool server. NOTE: You need to specify and administrator user in Code Review Tool here as only administrators have capability to create reviews on other user’s behalf.
Name Password
Type String
Required No
Description Specifies the password for the above administrator user name for the Code Review Tool server.
Name Depots
Type String
Required Yes
Description Specifies a list of depot names separated by comma, as listed in the <Depots/> section, for which reviews should be created on this code review server when change sets are checked into associated TFS projects.
Name StartReview
Type bool
Required No
Description Specifies whether to start the review after creating it, for all committers on the “Depots” specified above.
Protium Software Page 66 of 66 http://protiumsoftware.com
Committer element contains the following attributes:
Name Name
Type String
Required Yes
Description Specifies fully qualified account name of the committer in TFS collection. For e.g. “mydomain\tfsusername”.
Name Author
Type String
Required No
Description Specifies the account name in Code Review Tool server on behalf of whom the review needs to be created. If not specified, the committer user name from change set details is used for creating the review.
Name Reviewers
Type String
Required Yes
Description Specifies a list of account names in Code Review Tool server who should be added as reviewers for the created review.
Name StartReview
Type bool
Required No
Description Specifies whether to start the review after creating it for this particular committer when they check in a change set.