Skip to content Agility (Formerly VersionOne) Integration with TFVC and Jenkins VersionOne Integration

The integration of Agility with Team Foundation Version Control (TFVC) and Jenkins gives the development team complete control over the codes being committed in the source code repository. It also creates complete traceability for all workitems in Agility. With complete traceability for each work-item in the ecosystem, it is easier for enterprises to fulfil compliance requirements. Agility (Formerly VersionOne) – TFVC – Jenkins Integration Overview

In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between thecross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functionalcollaboration helps the teams get complete context of the business requirements.

Best-of-breed systems such as Agility, TFVC, and Jenkins bring rich functionalities to the ecosystem. When Agility is integrated with TFVC and Jenkins, all stakeholders have real-time visibility into the commits made by the development team. It is also easier to enforce authentic commits against each work item and access the changes/edits made to the commit files from Agility itself.

How Agility (Formerly VersionOne) – TFVC – Jenkins integration is beneficial for an enterprise

  • Track commit volume, track commit trends and edits/changes to commit files in real time
  • Enforce authentic commits to make sure each commit is happening against a scheduled and open workitem
  • Eliminate manual effort to close Agility workitem by automating the state transition on TFVC commit

How OpsHub Integration Manager integrates Agility (Formerly VersionOne), TFVC and Jenkins

OpsHub Integration Manager integrates Agility, TFVC andJenkins – all systems to each other bi-directionally. It ensures that alldata is available to each user, in that user’s preferred system, with fullcontext, in real-time. All the details related to a commit made against awork-item in Agility can be tracked from Agility itself. Forexample, for each commit that development team makes in TFVC, TFVC synchronizes a ‘commit entity’ linked to the specific requirementid back to Agility.

Popularly synchronized entities Agility TFVC Entities Mapping

Use Case: Agility (Formerly VersionOne) integration with TFVC & Jenkins

Problem statement: Pre-commit hooks can be configured to prevent faulty/erroneous check-ins.

Solution: If Agility and TFVC are integrated using OpsHub Integration Manager, the pre-configured hooks will prevent check-ins against a wrong/incorrect ID or a defect in an inactive sprint.

  1. A developer works on a ‘defect’ in Agility and runs a test case against it. The test case passes.
  2. The developer then commits against the ‘defect’ in TFVC.
  3. As the ‘defect’ against which the developer has committed is not in active sprint, when Jenkins runs a pre-scheduled test on it, the commit fails.
  4. The status of the commit synchronizes to Agility. Agility TFVC Jenkins Integration

Benefits of integration for Agility and TFVC users Agility (Formerly VersionOne) users

  • Traceability for business requirements throughout the ALM tool chain
  • Visibility into the volume, quality of commits, and commit trends in real-time

TFVC users

  • Each commit can be traced back to its respective workitem at any given point in time from TFVC itself
  • Enforced checkpoints ensure that no mandatory steps/checks are missed while making a commit – this leads to high success rate for commits