Skip to main content

TFS Integration Tools – March 2012 Release

Last month Microsoft  released a new version of the TFS Integration Tools on the Visual Studio Gallery.(with support for both Team Foundation Server 11 and Team Foundation Service.)

“The TFS Integration Tools is a project developed by the Team Foundation Server (TFS) product group and the Visual Studio ALM Rangers to integrate Team Foundation Server with third party systems for migration and synchronization of data.”

The list of fixed bugs is long(I recognize too much of them Winking smile):

General
  • TFS authorization error syncing with a hosted TFS
  • When in multi session mode, integration tools appear to have a memory leak in TfsIntegrationService.exe
Version Control
  • ClearCaseDetailedHistoryAdapter with the SnapshotStartPoint option create folders in TFS for files in ClearCase
  • Cloaked filter pairs should always be applied after non-cloaked filter pairs or a migration to TFS VC will fail
  • Detail History Adapter runs the lshistory command one level higher in the tree than specified by the filter pair causing problems
  • Infinite loop when migrating a changeset that contains a cyclic rename
  • lshistory command fails when there is a space in the ClearCase filter pair path
  • Merge+Branch operations in sync resulted in VC data corruption
  • Moving some files under a deleted folder causes the files to not be deleted on the other side
  • Resolving VC namespace conflicts results in System.InvalidOperationException: Sequence contains no elements
  • TFS VC Adapters throw NullReferenceException in ProcessChangeGroup() after initialization of MigrationProvider fails
  • VC Conflict Detection does not compare all of the possibly conflicting change groups after an error prevents the sync from reaching a sync point
  • VC Migration/Sync: A runtime error occurs rather than a named conflict for all Exceptions thrown when checking into TFS
  • VC named conflicts should stop the VC session until the conflicts are resolved (and not just stop the current round trip)
WIT
  • Adapter doesn't deal with the DB2 date format returned by some ClearQuest 2003 APIs
  • CheckBypassRulesPermission always throws conflict when using a Hosted TFS service in a WIT session
  • ClearQuest items don't migrate from ClearQuest servers that are not configured to use UTC times
  • ClearQuestMigrationConfigGenerator.exe fails to start on 64bit - should be removed from release
  • Conflict types TFSCyclicLinkConflictType and TFSMulitpleParentLinkConflictType should both support skip resolution actions
  • CQ UserMappings that ships with TFS should work on out-of-the-box 2-way sync
  • ServerDiff Wit command does not work when the ClearQuest credentials are stored in the Windows credentials cache
  • TFS11->TFS11 AddWorkItemTest fails because WIT Server Diff says System.ChangedDate is different
  • WIT field mapping: Using multiple mapped values with "@@MISSINGFIELD@@" fails the configuration validation - it should be allowed
Internal Dogfooding
  • Dogfood Sync (VC): conflict detection is skipped in certain scenario causing content mismatch
  • Dogfood Sync (VC): VC sync blocked by transient TFS condition (bad gateway) that can generate a named conflict that must be resolved to continue
  • Dogfood Sync (WIT): After resolving a WIT Edit/Edit conflict newer revs of the accepted work item will be migrated before the conflict work item rev is migrated
  • Dogfood Sync (WIT): Basic conflict detection phase is extremely slow on Dogfood WIT sync
  • Dogfood Sync (WIT): Runtime error blocking WIT sync
  • Dogfood Sync (WIT): Work items changes backlogged on a conflict that occurred when migrating the mirrored work item are not unblocked when the conflict is resolved
  • Dogfood Sync: The Tfs2012ShellAdapter UI doesn't work correctly for configuration or conflict resolution
  • Dogfood: WITServerDiff command does not compare links properly and reports other expected differences
  • Dogfood: WITServerDiffJob should support the "ServerDiff WIT" command line options as configurable settings
  • Dogfood: WITServerDiffJob takes OutOfMemoryException
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more