Contents:

  1. Introduction
  2. Requirements
  3. Configuring HP ALM
    1. Disabling
  4. Using the Integration
    1. How to update the source code information field
  5. Known Limitations

Introduction

This support is intended for users that would like some ALI-like functionality without having HP Application Lifecycle Intelligence (ALI) for ALM installed by adding SVN commit information to a requirement or defect. If you are using HP ALI, you do not need this feature.

Requirements

To use this integration, users must have one of the following Eclipse SVN clients installed along with the HP ALM connector:

It is recommended that when installing one of these integrations that you also install the associated Mylyn integration so that commit messages are automatically generated and properly formatted so that this integration works as expected. Note that installing the Mylyn integration for Subclipse or Subversive may automatically install Subclipse or Subversive, but will not install the SVN Client adapter. To access SVN within Eclipse, you must install an SVN client from the Subclipse or Subversive update site and select all required items.

Users must also have at least 1 SVN repository configured in Eclipse and HP ALM must be configured for the source code information field.

Configuring HP ALM

To use the SVN commit information feature, you will need to have the following items configured on the HP ALM server:

  1. The IDE Customization must be installed and available for the project
  2. A user defined field of type “Memo” must be created for both/either Defects or Requirements where the SVN commit information can be stored
  3. The IDE customization must map the “Source code information field” to the user defined Memo field that was created for Requirements and Defects

Once this configuration is complete, the next time that users refresh their repository configuration, they will see the new field for SCM information in the Task Editor for the requirements and defects that they were added to. This operation can be triggered by the user or will automatically occur once a day to ensure that the configuration is up-to-date

Disabling

If you wish to disable this feature, you can simply remove the source code information field mapping from the IDE Customization or mark the field as not visible to users for that project in HP ALM.

Using the Integration

This features provide source code traceability in HP ALM. The SVN integration retrieves the last changeset from SVN that was committed as a part of the given requirement or defect and updates the source code information field with the commit information. The requirement of defect that code was committed by is determined by the commit message that is generated when committing files while you have a task active. To use this feature effectively, users should follow the steps below to ensure that the field remains up-to-date.

How to update the source code information field

  1. Activate a requirement or defect in work on the feature or defect outlined by the task.
  2. When ready to commit, use the standard commit action for the SVN integration installed. The commit message should be automatically generated with information about the requirement or defect that was being worked on, removing the need to add any additional information upon commit.
  3. Open the task editor for the task that you were working on.
  4. Expand the source code information field in the task editor, select the SVN repository that you committed your code to and press the “Add Latest SVN Changeset” button
  5. Submit the task to HP ALM using the “Submit” button in the Task Editor toolbar or the “Actions” section to submit your changes to the server.

Known Limitations