selvakumar

About selvakumar

Leading the way: TeamForge Connector Server first sync platform supporting HP ALM 12

CollabNet Connector Framework

Just a couple of weeks after HP launched HP ALM 12, we are proud to announce full support for this version in our sync platform. TeamForge Connector Server 2.3.1 (aka CCF) is the first SLI (software lifecycle integration) platform that officially supports HP ALM 12. HP ALM 12 defects and requirements can be bi-directionally synchronized with CollabNet TeamForge trackers and planning folders. We support the traditional QC desktop client as well as the newly introduced HP ALM web client. Not related to HP ALM directly but to web clients in general, we noticed that not all of our customers were …

Read More »

Migrating Subversion Repositories to Git – The definitive Guide for TeamForge Users

gerritcollabnet

  Many software projects are moving from a centralized version control system (CVCS) to a distributed version control system (DVCS). Undoubtedly, the most used DVCS is Git. My team at CollabNet recently migrated one of our flagship Open Source projects, the CollabNet Connector Framework, from Subversion to Git. This blog shares the step by step guide to migrate SVN repositories  to Git repositories using git svn while maintaining all version history. This blog will cover two use cases: 1) Migration of a single project SVN repository to a single Git repository 2) Migration of a multi-project SVN repository to multiple Git repositories …

Read More »

Matching identities across ALM boundaries: Dynamic user lookup in CollabNet Connect

CollabNet-Connect-cloud-revised-739x357

ALM integration challenge #1: Same users but different accounts in different systems CollabNet Connector Framework (CCF) aka CollabNet Connect/sync is an Application Life-cycle Management (ALM) middle-ware that integrates and synchronizes data between CollabNet TeamForge and various ALM platforms like HP Quality Center/ALM 11, ScrumWorks Pro, MS Team Foundation Server and Rational ClearQuest. One of the most common use cases we encounter when doing artifact synchronization with CCF is that  user accounts are not identical on source and target systems. A user called John Doe may have an account jdoe in TeamForge and john_doe in Quality Center. To complicate things, certain users may not even …

Read More »