Integration with Jenkins.

[Valentin ZAPKeymaster]

Hi Abhinav Kumar,

Watch this video, it explains how to do that through direct Jenkins->ZAPTEST integration and through HP ALM.
https://www.youtube.com/watch?v=Eb6aoa_u8-0

Let us know if you have any additional questions.

[abhinav kumarParticipant]

hi,

I tried the Windows Batch Command. But I am getting error in Console of Jenkins

Can you please explain the Windows Batch Command to be used in detail or any other generic command that can be used to trigger the execution.

Regards.
Abhinav

[Sergey ZAPKeymaster]

Hi Abhinav Kumar,

1. There are plenty of information on the web how to install and use “psexec”. Please note, you need “psexec” only if you need to run a test on a remote machine.

2. ZAPTEST Command Line Interface usage:
ZAPTEST [options]
Without options provided, ZAPTEST will open the specified test

Options:
-r Runs the specified test
-h Hides the ZAPTEST window (forces -q option)
-q Quits ZAPTEST after test execution is complete
-nr Results are not opened after test execution
-rp path Custom results path location
-d Output debug information
-help Shows this help menu
/? same as -help

Usage Example:
ZAPTEST -r -h -d -nr “C:UsersuserDesktopdemo.zap”

[Valentin ZAPKeymaster]

Hey,

Yes, absolutely. Here’s more info:
[hr]
Perform the following on the machine where Jenkins is installed:

1. Download the Microsoft PsExec utility (it is a tool from microsoft that can launch applications on a remote machine): https://technet.microsoft.com/en-us/sysinternals/pxexec
2. Extract the archive from the downloaded file above
3. Copy the PsExec.exe file from the extracted archive to the following folder:
   jobsworkspace
   Example:
   C:Program Files (x86)JenkinsjobsZAPTEST Demoworkspace

[hr]

Before running the command in Jenkins, you can try it first in command window:

1. Open the workspace folder where the PsExec.exe is located. Example path:
   C:Program Files (x86)JenkinsjobsZAPTEST Demoworkspace
2. Hold the SHIFT keyboard key and right click inside the folder (on any empty space)
3. Click “Open command window here” to open the command shell
4. Type the PsExec command the same way you have it in Jenkins
5. Troubleshoot that it works here

For full PsExec command arguments, check this link:
https://technet.microsoft.com/en-us/sysinternals/pxexec[/li]

[Author]

Posts