Child pages
  • HPE Application Automation Tools

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note
iconfalse
titleContent Security Policy

Starting with version 1.641 (or 1.625.3), Jenkins introduced the Content-Security-Policy header. This causes some of the integration links, such as links to reports, to become inoperable. For details, see Configuring Content Security Policy and Changes in Jenkins to reduce XSS vulnerabilities . For suggested workarounds until the issue is resolved, see Content Security Policy Header.

...

  • If you are working with Quality Center 10.00 or earlier, and QuickTest Professional 9.x or 10.x, use the Quality Center Plugin.
  • If you are working with ALM Octane, make sure that you work with version 5.1 or later of this plugin, and that you do not have the HPE ALM Octane CI plugin installed. For more details, see Upgrade see Upgrade from the HPE ALM Octane CI plugin to this plugin.
  • For ALM Octane-UFT integration (without pipelines) or ALM Octane-Performance Center integration (using pipelines), make sure that you work with version 5.2 or later of this plugin.
  • ALM Octane supports working with CloudBees Jenkins Enterprise version 15.11 or later, with CloudBees Jenkins Operations Center version 1.8 or later.
  • ALM Octane can display a pipeline's structure only if it is built using one of the following:

...

Before you can create an ALM Octane pipeline, you must Configure the Connection to your ALM Octane Server.
To create an ALM Octane pipeline in Jenkins:

...

Note: These reports might require you to perform a Security header override. For details, see #Content see Content Security Policy Header.

...

Running Performance Tests using HPE Performance Center

...

  • At the end of a successful flow, Jenkins sends: done, left to send 0 events
    For example: 
    INFO - EventsClient: sending events [job\-name:STARTED] to 'http://localhost:8080'...
    INFO - EventsClient: sending events [job\-name:FINISHED] to 'https://mqast010pngx.saas.hpe.com'...
    INFO - EventsClient: ... done, left to send 0 events
    INFO - TestDispatcher: There are pending test results, connecting to the MQM server
    INFO - TestDispatcher: Successfully pushed test results of build job-name#10
  • When the ALM Octane server is not available, log messages may look like this:
    ERROR - BridgeClient: connection to MQM Server temporary failed: authentication error com.hp.mqm.client.exception.AuthenticationException: Authentication failed: code=503; reason=Service Unavailable

...