This plugin integrates Micro Focus products with Jenkins. Using the plugin, you can create and use virtual services, run Performance Center or LoadRunner performance tests, run UFT functional tests, run tests in your lab, and run tests on mobile devices. This plugin also lets you upload test results to ALM. In addition, ALM Octane users can track and trigger Jenkins pipelines from within the user interface.
Beginning version 5.5, this plugin will only support the latest five LTS versions of Jenkins (currently 2.60.3). This is a result of the Jenkins policy to no longer support older update centers. Jenkins 2.54 and higher requires you to have Java 8 installed on the machine. To recover any information lost during an upgrade relating to package names, backup the Jenkins folder and then run the Rebranding script.
Submit issues and feedback through JIRA
This plugin is open source. If you identify any issues or want to submit enhancement requests, please use JIRA. The component for this plugin is the hp-application-automation-tools-plugin component. Your feedback and involvement will allow us to stabilize and enhance the capabilities of the plugin. The latest, early access, beta versions of this plugin are available here.
|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 Jenkins Security Advisory . For suggested workarounds until the issue is resolved, see Content Security Policy Header.|
This version provides the following enhancements:
UFT (Unified Functional Testing)
SRF (StormRunner Functional)
ALM (Application Lifecycle Management)
PC (Performance Center)
This plugin supports the following Micro Focus product versions:
|Micro Focus tool||Supported versions||Find more information...|
ALM (Application Lifecycle Management) 12.xx
|12.xx||ALM Integration Jenkins page|
|ALM Lab Management||12.xx||ALM Integration Jenkins page|
|ALM Octane||12.53.20 or later (12.55.4 or later required |
for direct UFT integration and for PC integration using pipelines)
|ALM Octane Integration Jenkins page|
|LoadRunner||12.xx||LoadRunner Integration Jenkins page|
|Mobile Center (uploading apps)||2.0 - 2.80||Mobile Center Help|
|Performance Center||12.xx (12.53 or higher required for trend reports)||Performance Center Integration Jenkins page|
|Service Virtualization||3.80 - 4.20||Service Virtualization Integration Jenkins page|
|StormRunner Functional||1.40||StormRunner Functional Help Center|
|UFT Pro (LeanFT)||14.03 and higher|
|Unified Functional Testing (UFT)||12.xx and 14.03 or higher|
You can run client side-or server-side (Default or Functional) test sets and build verification suites from Application Lifecycle Management (ALM) or functional tests from the file system. You can create and configure ALM Octane pipelines from the ALM Octane user interface, or on Jenkins.
Due to rebranding in this version of the plugin to the "Micro Focus" name, certain job history and configurations from previous jobs may be not be recognized by Jenkins. Before you use this version of the plugin, back up all projects and jobs, and all job configurations related to the plugin that are included in the General Jenkins configuration. Run the following job to convert your earlier configurations:
Connect an execution node to the Jenkins server
To set up a pipeline test job for your Micro Focus testing tool:
Enter the stage and node arguments into the Script area. For example,
The available Pipeline job types are loadRunnerTest, uftScenarioLoad, runFromAlmBuilder, sseBuild, sseBuildAndPublish, pcBuild, svChangeModeStep, svDeployStep, svExportStep, and svUndeployStep.
Pipeline step name
Run LoadRunner performance tests from a file system scenario file
Run a UFT scenario from file system scenario
Execute functional tests from ALM
ALM Lab Management
Execute tests using ALM Lab Management
ALM Lab Management
Execute tests using ALM Lab Management and Publish tests result
Execute tests using Performance Center
Change the mode of a Virtual Service
Deploy a Virtual Service
Export a Virtual Service
Undeploy a Virtual Service
Pipeline jobs are not supported for Mobile Center uploads, ALM test uploader, and ALM AUT job types.
The available archive modes are:
In order to allow the add-in to support non-English languages, make the following changes to your Jenkins Master and nodes configuration:
<service> <id>jenkins</id> <name>Jenkins</name> <description>This service runs Jenkins continuous integration system.</description> <env name="JENKINS_HOME" value="%BASE%"/> <!-- This example assumes that you have java in your PATH. To run Jenkins with a specific version of Java, specify a full path to the desired java.exe. --> <executable>%BASE%\jre\bin\java</executable> <arguments>-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 "%BASE%\jenkins.war" --httpPort=8080 --webroot="%BASE%\war"</arguments> <!-- The *interactive* flag causes the empty black Java window to be displayed. <interactive /> --> <logmode>rotate</logmode> <onfailure action="restart" /> </service>
<service> <id>jenkinsslave-c__jkns</id> <name>jenkinsslave-c__jkns</name> <description>This service runs a slave for Jenkins continuous integration system.</description> <!-- This example assumes that you have java in your PATH. To run Jenkins with a specific version of Java, specify a full path to the desired java.exe. --> <executable>C:\Program Files (x86)\Java\jre1.8.0_91\bin\java.exe</executable> <arguments>-Xrs -jar "%BASE%\slave.jar" -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 -jnlpUrl http://xxx.xxx.xxx.xxx:8080/jenkins/computer/VM112233/slave-agent.jnlp -secret xyzabc</arguments> <!-- The *interactive" flag causes the empty black Java window to be displayed. <interactive /> --> <logmode>rotate</logmode> <onfailure action="restart" /> </service>
java -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 -jar slave.jar -jnlpUrl http://xxx.xxx.xxx.xxx:8080/jenkins/computer/VM112233/slave-agent.jnlp -secret xyzabc
Starting with version 1.641 (or 1.625.3), Jenkins introduced the Content-Security-Policy header. This prevents some of the links that appear in the integration to become inoperable. For example, the links to the LoadRunner Performance and UFT HTML reports will not work.
For UFT HTML and LoadRunner Performance reports, type the following line and press Run.
An additional option for LoadRunner Performance reports. Type the following line and press Run.
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "sandbox; default-src 'none'; img-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; child-src 'self';")
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "sandbox; default-src 'none'; img-src 'self'; style-src 'self'; script-src 'self'; child-src 'self';")
For best performance, it is recommended to install the testing tools and ALM/QC as nodes on slave machines, and not directly on the Jenkins server. For instructions on configuring nodes, see
On the Jenkins slave machine, make sure the the Jenkins Slave service is not logged in with the Local System account. To function properly, it should log in with an account the has administrator privileges.