By integrating TeamForge with GitHub and Jenkins, teams in the development and delivery ecosystem can create end-to-end traceability for each work-item and automate certain tasks that can, otherwise, consume manual effort hours.
This, in turn, helps in delivering a high-quality product to customers at a faster pace.
TeamForge – GitHub – Jenkins Integration Overview
In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a significant 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.
With best-of-breed systems such as TeamForge, GitHub, and Jenkins, all stakeholders get 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 TeamForge itself.
How TeamForge – GitHub integration is beneficial for an enterprise
- Access to commit details such as commit trends, number of files changes, etc. help identify quality risks on critical backlogs
- Enables automated continuous integration & continuous delivery
- Helps meet all regulatory compliance standards by enforcing commit rules against TeamForge
How OpsHub Integration Manager integrates TeamForge, GitHub, and Jenkins
OpsHub Integration Manager integrates TeamForge and GitHub. The details of commits made in GitHub against a work item ID in TeamForge can be tracked from TeamForge itself. Therefore, it’s easier to track details such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’ for each commit. The integration of Jenkins with TeamForge and GitHub helps in bringing automation in the process. For example, Jenkins automates the closure of TeamForge work item on a successful code commit in GitHub.
Popularly synchronized entities
Use Case: TeamForge Integration with GitHub and Jenkins
Problem statement: No control on backlogs getting committed – therefore, anyone can commit on a requirement/defect that is not even present in the active sprint.
Solution: : If TeamForge, GitHub, 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.
- The developer commits the code in GitHub against a ‘requirement’ in TeamForge.
- As the ‘requirement’ 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 TeamForge.
Benefits of integration for TeamForge, GitHub and Jenkins users
- 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 work item
GitHub and Jenkins users
- Each commit can be traced back to its respective work item at any given point in time from GitHub itself
- Eliminate manual effort by automating the change in work item status in TeamForge on successful/unsuccessful code commit in GitHub