Skip to content

Jenkins Integration with Rally Software & GitHub

Jenkins Integration

The integration of Jenkins with Rally Software and GitHub gives the development team complete control over the codes being committed in the source code repository. It also creates complete traceability for all workitems in Rally Software. With complete traceability for each workitem in the ecosystem, it is easier for enterprises to fulfill compliance requirements.

Download Datasheet Contact Us

Jenkins – Rally Software & GitHub 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 Jenkins, Rally Software and GitHub bring rich functionalities to the ecosystem. When GitHub is integrated with Rally Software 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 Software itself.

How Jenkins – Rally Software – GitHub 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 Software workitem by automating the state transition on GitHub commit

With Jenkins + Rally Software Software + GitHub integration, enterprises can:

Jenkins Rally Software GitHub Integration

How OpsHub Integration Manager integrates Jenkins, Rally Software and GitHub

OpsHub Integration Manager integrates Jenkins with Rally Software and GitHub.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 Rally Software can be tracked from Rally Software itself. For example, for each commit that development team makes in GitHub,GitHub synchronizes a ‘commit entity’ linked to the specific requirement is back to Rally Software. Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’. The integration of Jenkins also ensures elimination of developer’s effort to close Rally Software workitem by automating the state transition on GitHub commit.

Entities that can be synchronized between Jenkins, Rally Software and GitHub

Jenkins Rally Software GitHub Entities Mapping

Use Case: Jenkins integration with Rally Software and GitHub

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 Software, 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.

  1. A developer works on a ‘user story’ in Rally Software and runs a test case against it. The test case passes.
  2. The developer then commits against the ‘defect’ in GitHub.
  3. 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.
  4. The status of the commit synchronizes to Rally Software.
Jenkins Integration with Rally Software GitHub

Benefits of integration for Jenkins, Rally Software and GitHub users

Jenkins and Rally Software users

  • Complete traceability from Rally Software to source code in GitHub
  • Visibility into the volume, quality of commits, and commit trends in real-time
  • Automation introduced through Jenkins saves time
  • Reduced dependency on manual communication to track the completion of a task

GitHub 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
  • Automation introduced through Jenkins saves time

Check Jenkins integration with other systems