SCM integration allows ALI to extend traceability of HP ALM towards information about code changes coming from SCM repositories. It allows you to monitor SCM changes and keep traceability between source code, requirements, defects and builds. In addition, you can define SCM policies that control committed changes. You can use SCM integration without "touching" your SCM repository. ALI allows for periodic retrieval of code changes. If you are interested in real-time monitoring of changes or SCM policy enforcement, you have to install an agent into your SCM repository. The agents are available in the ALI Bundle (download from ALI Bundle->CONTENT - select the agent depending on you SCM and operating system).


Out of the box supported Source Code Management (SCM) systems:

  • Subversion (SVN)
  • Concurrent Versions System (CVS)
  • Microsoft Team Foundation Server (TFS)
  • Perforce
  • GIT (available in HP ALI 2.6 and higher)


ALI also provides open APIs that allow for integration with custom SCM systems.



Additional SCM integrations:

  • OpsHub, an HP AllianceONE Partner,  provides an integration of HP ALI with IBM Rational ClearCase. For more information on how to use OpsHub' plugin, and review a short demonstration of the solution, visit this site.
  • AccuRev provides integration of HP ALI with AccuRev 5.X


Source Code Traceability

When integrated with an SCM system, ALI automatically tracks code changes and links them with related ALM entities: requirements, defects, builds, releases. This makes it easy to find out:

  • Code changes implementing a requirement or defect.

  • Code changes implemented in specific builds.
  • What specifically was implemented during a specific time period, release, build or by an individual contributor.
  • Which requirements and defects are affected.
  • Amount of changes associated with a particular requirement.
  • Line by line differences in change sets.
  • Changes not associated with either requirements or defects.
  • Build & Quality metrics.
  • Aggregated information about code coverage, test results and amount of changes.


SCM Policy Enforcement: Control changes committed to SCM

With ALI, it is possible to define SCM policies that control committed changes. The enforcement of the SCM policies helps to ensure that developers follow prescribed guidelines and best practices. Team leaders will be confident that developers implement the right features and add required metadata to the committed change sets. Policy enforcement also provides invaluable help during stabilization periods as it is easy to ensure that developers fix only severe defects or to lock the code base of a release completely.


Syndicate content