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 VersionOne, TFVC, and Jenkins bring rich functionalities to the ecosystem. When VersionOne 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 VersionOne itself.
How 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 VersionOne workitem by automating the state transition on TFVC commit
How OpsHub Integration Manager integrates VersionOne, TFVC and Jenkins
OpsHub Integration Manager integrates VersionOne, 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 VersionOne can be tracked from VersionOne itself. Forexample, for each commit that development team makes in TFVC, TFVC synchronizes a ‘commit entity’ linked to the specific requirementid back to VersionOne.
Popularly synchronized entities
Use Case: VersionOne integration with TFVC & 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 VersionOne and TFVC users
- Traceability for business requirements throughout the ALM tool chain
- Visibility into the volume, quality of commits, and commit trends in real-time
- 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
Check VersionOne integration with other systems
VersionOne – TFVC – ServiceNowVersionOne – Azure DevOps (VSTS)VersionOne – Azure DevOps Server (TFS)VersionOne – Subversion – JIRAVersionOne – Helix ALMVersionOne – SalesforceVersionOne – JIRAVersionOne – Micro Focus ALM/QCVersionOne – ServiceNowVersionOne – GitHub – ZendeskVersionOne – qTest – JenkinsVersionOne – DOORS NG