How to activate Shared Parameters feature on a team project upgraded from TFS 2013 to TFS 2013.2 update

by Xavier Dilip Kumar 24. April 2014 20:01

Explanation:

After updating TFS 2013 server with update TFS 2013.2, Shared Parameters feature need to be activated manually for each team project. This feature provides to testers and test leads the ability to manage test parameter data at one place by using Shared Parameters. Any subsequent changes to parameter data can be updated at one place and all the test cases referencing the Shared Parameter are automatically updated

Solution:

  • Open team project web access.
  • Click on "Test" tab --> "parameters" option

          

  • Click on "Configure feature" option.

          

  • Click on "Verify" & "Apply" button

Tags: ,

Difference between Visual Studio Scrum 2013 and Visual Studio Scrum 2013.2 Process Template

by Xavier Dilip Kumar 24. April 2014 19:46

Explanation:

  • Visual Studio Scrum 2013.2 Process Template has support for Shared Parameters which will enable testers the ability to manage test parameter data centrally. New Shared Parameter work item type, category, and link type are updated to the process template.
  • The ProductBacklog.wiq and SprintBacklog.wiq queries have been removed

Tags:

TFS 2013

Work item history display revision change even though no field values were updated

by Xavier Dilip Kumar 15. April 2014 13:36

Impact:

  1. History displays all changes to Rev field through service account when iteration path nodes are modified
  2. Changed date and Changed by field values are updated automatically

Reason:

This issue occur when we rename, move, or make any changes to the iteration path nodes in TFS web portal settings.

More Details

Tags:

TFS 2012 | TFS 2013

After applying update 2, not able to connect to TFS 2013 server with Urban Turtle 4.16 installed

by Xavier Dilip Kumar 15. April 2014 06:20

Exceptions:

Client exception: TF31002 : Unable to connect to this Team Foundation Server

Server exception:  Could not load type 'Microsoft.TeamFoundation.Server.WebAccess.Routing.SupportedRouteAreaAttribute' from assembly 'Microsoft.TeamFoundation.Server.WebAccess, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.

Explanation:

Looks like there are compatibility issues with Urban Turtle 4.16 or earlier with TFS 2013 Update 2. You will see the above exceptions, as soon as you apply update 2 on TFS 2013 server with Urban Turtle 4.16 installed.

Solution:

You need to uninstall Urban Turtle 4.16 or earlier and install Urban Turtle 4.16.1. You will end up with the following error while uninstalling Urban Turtle 4.16 after applying Update 2. 

Urban Turtle 4.16 is not compatible with this version of Team Foundation Server 2013. Please make sure that you are running Team Foundation Server 2013 (RTM, build 21005.01) or download a compatible version from our website.

Workaround to uninstall Urban Turtle 4.16 or earlier: 

1. Use TFSServiceControl quiesce command to ensure that all necessary operations, services, and application pools are stopped for maintenance tasks

  • TFSServiceControl quiesce

2.Launch the Registry Editor (c:\windows\regedit.exe)

2.Navigate to key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TeamFoundationServer\12.0'

3.Double-click on the 'BuildNumber' entry

4.Change the value to 21005.01

5.Uninstall Urban Turtle 4.16

6.Restore the value of 'BuildNumber' back to '30324.00'

7. Use TFSServiceControl unquiesce command to start all necessary operations, services, and application pools for TFS

  • TFSServiceControl unquiesce 

8.Install Urban Turtle 4.16.1

Reference

 

Tags:

TFS 2013

How to install TFS update on TFS Servers?

by Xavier Dilip Kumar 9. April 2014 20:32

STEPS:

1. Log on to your TFS App tier

Note : Make sure you had backed up all databases related to TFS before installing the update

2. Use TFSServiceControl quiesce command to ensure that all necessary operations, services, and application pools are stopped for maintenance tasks

  • TFSServiceControl quiesce

3. Install the update.

4. Run the TFS Admin console tool to configure the TFS App Tier for installed update.

5. Use TFSServiceControl unquiesce command to start all necessary operations, services, and application pools for TFS

  • TFSServiceControl unquiesce 

If you have multiple app tier(s), proceed with step 1 to 3 on each app tier one by one first and then proceed with step 4 and 5 on each app tier one by one.

Tags: ,

TFS 2012 | TFS 2013

How to clone a build definitions from one project to another within a same collection?

by Xavier Dilip Kumar 7. March 2014 12:31

Solution:

You can use TFS power tools command line utility to clone a build definition across projects

Note: You can download and install TFS Power Tools from http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f

1. Open "Visual Studio" command prompt

2. You can use the following command to preview the build definition clone

tfpt builddefinition /clone "<Source Team Project Name>\Build Definition" "<Target Team Project Name>\Build Definition" /Collection:http://tfs:8080/tfs/DefaultCollection /preview

3. You can use the following command to clone the build definition

tfpt builddefinition /clone "<Source Team Project Name>\Build Definition" "<Target Team Project Name>\Build Definition" /Collection:http://tfs:8080/tfs/DefaultCollection

Only the well-defined build definition can be cloned using this approach meaning the build source build definition should have all the mandatory (required) properties filled with values

For example:

The source build definition without Build controller name cannot be cloned using this approach.

You can also use * wildcard character to clone all build definitions at one shot, provided you have well-defined build definition at source team project.

tfpt builddefinition /clone "<Source Team Project Name>\*" "<Target Team Project Name>\"  /Collection:http://tfs:8080/tfs/DefaultCollection

Remember to update the following build properties to the cloned build definition. 

1. Disable build definition to prevent accidental triggering.

2. Change workspace mapping to target team project source.

3. Change drop location.

4. Change the build process template to point to the right projects.

5. If you use custom build workflow/tasks, make sure your build controller custom assembly references are pointed to target team project source control

6. Enable the build definition.

 

Tags: , ,

TFS 2010 | TFS 2012 | TFS 2013

About the author

My name is Xavier Dilip Kumar Jayaraj and I am a Software Configuration Management Engineer with a background in application development, Build & packaging using Install Shield.

Profile in LinkedIn

  

Quotes I Like

"Failure will never overtake me if my determination to succeed is strong enough."  - Dr. APJ. Abdul Kalam

"Always be yourself, express yourself, have faith in yourself, do not go out and look for a successful personality and duplicate it." - Bruce Lee

"Technology is just a tool. In terms of getting the kids working together and motivating them, the teacher is the most important." - Bill Gates

"Innovation distinguishes between a leader and a follower." - Steve Jobs

Disclaimer

The information provided here is based on my expreriences, troubleshooting and online/offline findings. It can be used as is on your own risk without any warranties and I impose no rights.

Month List