CA Agile Central – 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 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 RALLY, Jenkins, and GitHub bring rich functionalities to the ecosystem. When GitHub is integrated with RALLY 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 RALLY itself.
How CA Agile Central – GitHub – 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 RALLY workitem by automating the state transition on GitHub commit
With RALLY + GitHub + Jenkins integration, enterprises can:
How OpsHub Integration Manager integrates RALLY, GitHub, and Jenkins
OpsHub Integration Manager integrates RALLY with GitHub and Jenkins.It ensures that all data is available to each user, in that user’s preferredsystem, with full context, in real-time. All the details related to a commitmade against a work-item in RALLY can be tracked from RALLY itself. Forexample, for each commit that development team makes in GitHub,GitHub synchronizes a ‘commit entity’ linked to the specific requirement idback to RALLY. Each ‘commit entity’ includes information such as ‘who didthe commit?’, ‘when was the commit done?’, and ‘which part of the codewas committed?’. The integration of Jenkins also ensures elimination ofdeveloper’s effort to close RALLY workitem by automating the statetransition on GitHub commit.
Popularly synchronized entities
Use Case: RALLY integration with GitHub 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 RALLY, 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.
- A developer works on a ‘user story’ in RALLY and runs a test case against it. The test case passes.
- The developer then commits against the ‘defect’ in GitHub.
- 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 RALLY.
Benefits of integration for CA Agile Central RALLY and GitHub users
- Complete traceability from RALLY to source code in GitHub
- Visibility into the volume, quality of commits, and commit trends in real-time
- Reduced dependency on manual communication to track the completion of a task
- 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