User Guide | 2019.2

Adding Helix Versioning Engine source control providers

Add a Helix Versioning Engine provider to specify a source control integration connection for the Helix ALM project. This makes it easier for users to set up the integration in Helix ALM because the server connection is already configured. See Third-Party Integrations for a list of supported versions.

If your team uses Helix Swarm, you can specify the URL to provide hyperlinks to source files and changelists on the Helix ALM item Source Files tab and in other areas, such as reports.

Note:  You must also add a provider if you use triggers to allow users to attach changelists to Helix ALM issues, test cases, and requirements from Helix VCS clients.

1. Choose Tools > Administration > Source Control Providers.

The Source Control Providers dialog box opens.

2. Click Add.

3. Enter the provider Name. You can enter up to 256 characters. Provider names must be unique.

4. Select Helix Versioning Engine as the Type.

5. Enter the Helix Versioning Engine Server address and Server port.

6. If you use Swarm, enter the base Helix Swarm URL to provide hyperlinks to attached source files and changelists.

This base URL is automatically appended with the appropriate path for attachments on the Source Files tab in Helix items. For example, if the Swarm URL is http://swarm.wysicorp.com, the following hyperlink formats are used:

  • Files—http://swarm.wysicorp.com/file/<depot_file_path>?v=<file_version>
  • Changelists—http://swarm.wysicorp.com/changes/<changelist_number>

7. Click OK to save the provider.

After the provider is added, it is available to select in the Source Control Integration Local Options dialog box when users enable the integration. See Configuring source control integration.

Note:  The read-only Provider key field and Active option are only used if you add Helix Versioning Engine triggers to allow users to attach changelists to Helix ALM items from Helix VCS clients. The provider key is required in the script that runs the triggers and Active must be selected. See Configuring triggers to attach changelists from Helix VCS clients to Helix ALM items.