TFVC VersionOne 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 VersionOne, Jenkins, and TFVC bring rich functionalities to the ecosystem. When TFVC is integrated with VersionOne 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 VersionOne itself.
How TFVC – VersionOne – 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 VersionOne workitem by automating the state transition on TFVC commit
With TFVC, VersionOne, Jenkins integration, enterprises can:
How OpsHub Integration Manager integrates TFVC, VersionOne, and Jenkins
OpsHub Integration Manager integrates TFVC, VersionOne, and Jenkins – all systems to each other bi-directionally. It ensures that all 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 VersionOne can be tracked from VersionOne 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 VersionOne.
Popularly synchronized entities
Use Case: TFVC integration with VersionOne & Jenkins
Problem statement: Pre-commit hooks can be configured to prevent faulty/erroneous check-ins.
Solution: If VersionOne 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.
- A developer works on a ‘defect’ in VersionOne 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 VersionOne.
Benefits of integration for TFVC and VersionOne 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
- Visibility into the volume, quality of commits, and commit trends in real-time