Set up CI servers

This topic describes how to set up the connection between ALM Octane and a CI server such as Jenkins or TeamCity. This is the basis for working with pipelines in ALM Octane and for integrating ALM Octane with UFT.

Caution: The permission mechanism of ALM Octane Help is not synchronized with the permission mechanism of the CI server.

Therefore, ALM Octane Help users may have access to information from the CI server that they would otherwise not be authorized to access. For example, log files, stack traces an so on.

See also:

DevOps admin permissions are required.

Prerequisites: Obtain API access and make sure your CI server is supported

  • Obtain API Access. Ask your shared space admin for an API access Client ID and Client secret. The plugin uses these for authentication when communicating with ALM Octane.

    The shared space admin can obtain the Client ID and Client secret in ALM Octane Settings. The access keys must be assigned the CI/CD Integration role in all relevant workspaces. For details, see Set up API access.

  • Obtain access to a CI server that meets the necessary requirements. For the CI servers that are supported by the ALM Octane CI plugins, see CI Servers.

    For a list of plugins that must be installed on the Jenkins server to enable ALM Octane integration, as well as plugins that are supported by the ALM Octane integration but not required, see HPE Application Automation Tools wiki page.

Back to top

Install the ALM Octane CI plugin on your CI server

Download, install, and configure the plugin that enables ALM Octane integration with your CI server.

This plugin enables ALM Octane to retrieve and display your CI server's build pipelines, synchronize test run results with the CI server, and trigger pipeline runs on the CI server.

Plugins for Jenkins, TeamCity, Bamboo, and TFS are available online. For Jenkins, this functionality is part of the HPE Application Automation Tools plugin.

For other CI servers, build your own plugin in Java using the CI Plugin SDK for ALM Octane available on GitHub.

For details, see Install and configure the ALM Octane CI plugin on your CI server.

Back to top

Add CI servers on ALM Octane

For ALM Octane to integrate with a CI server, the servers and their URLs must be added in ALM Octane.

  1. In Settings , click Spaces and select a workspace.

  2. Click the DevOps tab. On the left side of the pane, select CI Servers.

  3. Click + to add a CI server and enter a name for the server.

  4. Select a URL from the list of CI servers.

    The list displays all servers that meet the following conditions:

    • The server has the ALM Octane CI plugin installed and configured to access your ALM Octane.

    • The API Access keys that the plugin is using are assigned the CI/CD Integration role in the current workspace.

You can now create pipelines in ALM Octane that reflect the ones running on the CI server.

Back to top

Manage your CI servers

In the list of CI servers, you can add or remove CI servers, view information about each server, and suspend or resume the connection between ALM Octane and the CI server.

Open the list of CI servers

This list provides information about the servers' status, type, URL, and more.

  1. In Settings , click Spaces and select a workspace.

  2. Click the DevOps tab. On the left side of the pane, select CI Servers.

    The list displays all servers that are set up with the ALM Octane CI plugin to access your ALM Octane.

  3. Select the columns that you want displayed. For example, for each server, you can see:

    • Whether the server is currently connected.

    • The CI server type.

    • The version of the plugin installed on the server, or the SDK version used to develop the plugin.

      Keep your plugin up-to-date to benefit from all the latest enhancements and functionality.

Suspend and resume data transfer from Jenkins to ALM Octane

Instruct a selected CI server to stop sending information to ALM Octane. This includes information such as pipeline runs, test runs, SCM commits, and code coverage data.

A suspension may be useful, for example, in the following situations:

  • Your CI server is undergoing maintenance and you don't want experimental data to be sent to ALM Octane.

  • You are investigating unexpected behavior on your CI server and you want to isolate the server.

  • The network between your CI server and ALM Octane is going to be disconnected for maintenance and you want to reduce overload on the CI server during that time.

To suspend or resume the connection between your CI server and ALM Octane:

Select a CI server and click the Suspend CI server input to ALM Octanebutton.

Note: The suspension is immediate, but it may take some time before the button in ALM Octane reflects the change.

Select a CI server and click the Resume CI server input to ALM Octane button to reconnect the CI server to ALM Octane.

Back to top

Next steps: