GitHub – Blueprint 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 brings in collective wisdom to take better decisions, faster.
Best-of-breed systems such as Blueprint and GitHub bring rich functionalities to the ecosystem and make the work of the product and development team easier. With Blueprint and GitHub integrated within the ecosystem, product development has real-time visibility into the commits made by the development team. It is also easier for them to enforce authentic commits against each work item and access the changes/edits made to the commits from Blueprint itself.
How GitHub – Blueprint 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
With GitHub + Blueprint integration, enterprises can:
How OpsHub Integration Manager integrates GitHub and Blueprint
OpsHub Integration Manager integrates Blueprint and GitHub 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 Blueprint can be tracked from Blueprint itself. For example, for each commit that the development team makes in GitHub, GitHub synchronizes a ‘commit entity’ linked to the specific requirement id back to Blueprint. Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’.
Entities that can be synchronized between GitHub and Blueprint
Use Case: GitHub integration with Blueprint
Problem statement: Lack of commit traceability in the Application Lifecycle Management (ALM) ecosystem can lead to compliance as well as other issues.
- The Product Manager creates a ‘business requirement’ in Blueprint.
- The development team works on the requirement, tests it, and then commits it in GitHub against the ‘requirement id’ specified in Blueprint.
- For each commit that happens from the development team, OpsHub Integration Manager synchronizes a ‘commit entity’ linked to the specific requirement id back to Blueprint. Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’.
Benefits of integration for GitHub and Blueprint users
- Each commit can be traced back to its respective workitem at any given point in time from GitHub itself
- Enforced checkpoints ensure that no mandatory steps/checks are missed while making a commit – this leads to high success rate for commits
- Complete traceability from Blueprint to source code in GitHub
- Visibility into the progress of development work, the volume and quality of commits made with full context, in real-time
- Reduced dependency on manual communication to track the completion of a task