I've been asked about this issue: how to create multiple build controllers on a single machine.
First of all: Why should we? This is needed in a TFS environment with many TFS Team project collections. Each build controller can serve one TFS Team project collection only.
So assuming we have a build machine strong enough for handling massive amount of builds from several collections, we are forced to provide multiple machines to host each controller.
The workaround - Unsupported! - is to setup a multiple build controllers environment on a single machine,
here's 2 posts about it:
TFS 11 provides a new way to use source control with TFS. Until TFS 11: The source control management is done entirely by the server. We have to report TFS when we make our local changes: when we want to add, delete, or edit files, for examples. Files have read only access, and TFS permits us to update files after we check out. Needless to mention, working disconnected from TFS is almost impossible. We can continue working on...
Started using TFS 11 Beta. Great features. Great improvements. Amazing new features in Team Explorer 11 for the developers, check Brian Harry’s post here. Rich, fast, and re-written user interface. But let’s talk about the web interface. TFS web interface becomes a main tool for administrating the team project and for the project management. TFS 11 is smarter: we manage “Teams”. Team has members. We set the areas & iterations that are relevant to the team. We set each member’s capacity to an iteration. At last, iterations have start & end dates. So TFS can help us and detect...
New version of Power Tools for TFS 2010 released.It contains updates for backup plan wizard (for example - no more retention duration minimum of 30 days),updates for windows shell extension (that enables youto manage workspaces, shelve/unshelve, view history...) andupdates for command line utility (for buils management).Read about it here.Download here.Also, new version of build extensions for java environment available here.Dan
Team Foundation Sidekicks by Attrice Corporation is a free-to-use suite of tools for Microsoft Team
administrators and advanced users.These tools provide Graphic User Interface for administrative
and advanced version control tasks in
multi-user TFS environments.
I was performing a conversion from Visual Source Safe to Team Foundation Server, using SRL’s legendary check list. Phase 1 – Analyzing using VSS tool, completed successfully. Phase 2 – Analyzing using TFS tool (VSSConverter analyze) – could not start because of an error: TF60008: The VSS database version is older than 6.0. The VSS converter only supports database versions 6.0 or above. Please upgrade the database version and try again. Visual Source Safe database must be converted to version 6 before TFS migration, but how? The Solution (Thanks to Leon Langleyben)...
I made some modifications on a work item definition, specially regarding to the state transitions. I uploaded my modifications to the server (TFS 2008 SP1), and performed refresh in my team explorer to view the changes. Everything OK.
But when I tried to view my modifications using Team System Web Access – I saw the old definitions. “Refresh cache” option did not help.
I googled it and found a post providing the solution: use the magic word - iisreset.
Before TFS 2010, renaming work item definition was a complex task. What we had to do was to create a NEW definition using the new name and all other definitions of the original work item, and to re-create all work items and lose all modification history. In TFS 2010, all we have to do is to rename work item definition using command line tool witadmin.exe Dan