TFVC, Jira, and Jenkins Integration Overview
In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements.
Best-of-breed systems such as Jira, Jenkins, and TFVC bring rich functionalities to the ecosystem. When TFVC is integrated with Jira 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 Jira itself.
How TFVC, Jira, and, 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 Jira workitem by automating the state transition on TFVC commit
With TFVC, Jira, and Jenkins, enterprises can:
How OpsHub Integration Manager integrates TFVC, Jira, and Jenkins
OpsHub Integration Manager integrates TFVC, Jira, and Jenkins bi-directionally. It ensures that all historical and current data is available to each user, in that user’s preferred system, with full context, in real-time. All the details related to a commit made against a work-item in Jira can be tracked from Jira itself. For example, for each commit that development team makes in TFVC, TFVC synchronizes a ‘commit entity’ linked to the specific requirement id back to Jira.
Popularly synchronized entities
Use Case: TFVC integration with Jira and Jenkins
Problem statement: No control on backlogs getting committed – therefore, anyone can commit on a defect that is not even present in the active sprint.
Solution: If Jira, TFVC, and Jenkins are integrated using OpsHub Integration Manager, then OpsHub Integration Manager can put a check that user can only commit on a defect that is present in active sprint.
- A developer works on a ‘defect’ in Jira and runs a test case against it. The test case passes.
- The developer then commits against the ‘defect’ in TFVC.
- 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.
- The status of the commit synchronizes to Jira.
Benefits of integration for TFVC and Jira 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
- Traceability for business requirements throughout the ALM tool chain
- Direct visibility into customer issues and their priorities
- Visibility into the volume, quality of commits, and commit trends in real-time