Hi Simon,

Thanks for reporting this in a separate defect report and many thanks for your feedback.

Could you please try to create a new freestyle project or use an existing one in which you delete the old Performance Center build step and recreate a new one from scratch (do not use a build step created with a previous version of this plugin).

Please let me know if the job runs correctly in it.

Regards,
Daniel

attaching logs screenshot from a run in my environment with the new plugin.

Started by user unknown or anonymous
Building in workspace C:\Jenkins_Home\workspace\Performance Center example job2
Mon 07.23.2018 at 11:01:35 AM BST - plugin version is '5.4.3-beta-SNAPSHOT'
Mon 07.23.2018 at 11:01:35 AM BST - Validating parameters before run
Mon 07.23.2018 at 11:01:35 AM BST - OK
Mon 07.23.2018 at 11:01:35 AM BST - Trying to login
[PCServer='xyz', User='abc.123']
Mon 07.23.2018 at 11:01:35 AM BST - Login succeeded
Mon 07.23.2018 at 11:01:35 AM BST - Searching for available Test Instance
Mon 07.23.2018 at 11:01:36 AM BST - Found testInstanceId: 375
Mon 07.23.2018 at 11:01:36 AM BST -
Executing Load Test:
====================
Test ID: 1764
Test Instance ID: 375
Timeslot Duration: 0:30(h:mm)
Post Run Action: Collate Results
Use VUDS: false
====================

Mon 07.23.2018 at 11:01:48 AM BST -
Run started (TestID: 1764, RunID: 1908, TimeslotID: 4005)

Mon 07.23.2018 at 11:01:53 AM BST - Error: executeRequest exception: Operation failed. Error code: 1001
Mon 07.23.2018 at 11:01:53 AM BST - Error: Run could not start!
Mon 07.23.2018 at 11:01:54 AM BST - Logout succeeded
Mon 07.23.2018 at 11:01:54 AM BST - Empty Results
Mon 07.23.2018 at 11:01:54 AM BST - Result Status (PC RunID: 1908): FAILURE

Build step 'Execute performance test using Performance Center' changed build result to FAILURE
Recording test results
RunResultRecorder: didn't find any test results to record
Finished: FAILURE

This is from a new freestyle project, using the same Performance Center scenario. I also tried with a new Performance Center scenario;

Started by user unknown or anonymous
Building in workspace C:\Jenkins_Home\workspace\Performance Center example job2
Mon 07.23.2018 at 11:09:10 AM BST - plugin version is '5.4.3-beta-SNAPSHOT'
Mon 07.23.2018 at 11:09:10 AM BST - Validating parameters before run
Mon 07.23.2018 at 11:09:10 AM BST - OK
Mon 07.23.2018 at 11:09:10 AM BST - Trying to login
[PCServer='xyz', User='abc.123']
Mon 07.23.2018 at 11:09:10 AM BST - Login succeeded
Mon 07.23.2018 at 11:09:10 AM BST - Searching for available Test Instance
Mon 07.23.2018 at 11:09:11 AM BST - Could not find available TestInstanceID, Creating Test Instance.
Mon 07.23.2018 at 11:09:11 AM BST - Searching for available TestSet
Mon 07.23.2018 at 11:09:11 AM BST - Creating Test Instance with testID: 1771 and TestSetID: 611
Mon 07.23.2018 at 11:09:13 AM BST - Test Instance with ID : 377 has been created successfully.
Mon 07.23.2018 at 11:09:13 AM BST -
Executing Load Test:
====================
Test ID: 1771
Test Instance ID: 377
Timeslot Duration: 0:30(h:mm)
Post Run Action: Collate Results
Use VUDS: false
====================

Mon 07.23.2018 at 11:09:25 AM BST -
Run started (TestID: 1771, RunID: 1909, TimeslotID: 4006)

Mon 07.23.2018 at 11:09:29 AM BST - Error: executeRequest exception: Operation failed. Error code: 1001
Mon 07.23.2018 at 11:09:29 AM BST - Error: Run could not start!
Mon 07.23.2018 at 11:09:30 AM BST - Logout succeeded
Mon 07.23.2018 at 11:09:30 AM BST - Empty Results
Mon 07.23.2018 at 11:09:30 AM BST - Result Status (PC RunID: 1909): FAILURE

Build step 'Execute performance test using Performance Center' changed build result to FAILURE
Recording test results
RunResultRecorder: didn't find any test results to record
Finished: FAILURE
 

Hi Simon,

Could you please try to execute the test by launching it from Performance Center itself? Perhaps the problems come from Performance Center server itself and not from the plugin.

regards,
Daniel

Continued from JENKINS-52366 :

danieldanan. I had build new project from scratch, but still I got the same exception :
Started by user
Umesh S G
Building in workspace C:\Program Files (x86)\Jenkins\workspace\PCTest
Mon 07.23.2018 at 03:57:55 PM IST - plugin version is '5.4.3-beta-SNAPSHOT'
Mon 07.23.2018 at 03:57:55 PM IST -

• - -
  Test description: PC Test
  Mon 07.23.2018 at 03:57:55 PM IST - Validating parameters before run
  Mon 07.23.2018 at 03:57:55 PM IST - OK
  Mon 07.23.2018 at 03:57:55 PM IST - Trying to login
  [PCServer='
  http://http://abc-xxx-g-xxx02.com/loadtest/General/Login.aspx?logout=1
  ', User='abcdef']
  Mon 07.23.2018 at 03:57:58 PM IST - Login succeeded
  Mon 07.23.2018 at 03:57:58 PM IST - Searching for available Test Instance
  Mon 07.23.2018 at 03:57:59 PM IST - getCorrectTestInstanceID failed, reason: com.thoughtworks.xstream.mapper.CannotResolveClassException: htmlMon 07.23.2018 at 03:57:59 PM IST - java.lang.NumberFormatException: null
  Mon 07.23.2018 at 03:58:01 PM IST - Logout succeeded
  Mon 07.23.2018 at 03:58:01 PM IST - Empty Results
  Mon 07.23.2018 at 03:58:01 PM IST - Result Status: FAILURE
• - -
  Build step 'Execute performance test using Performance Center' changed build result to FAILURE
  Finished: FAILURE

In my case the Performance Center side of things works fine, even based on the build job. These are the two runs from the 'failures' above. 

The two runs do start and complete successfully, despite what the Jenkins job thinks. 

Hi Simon,

Thanks for this verification.

Could you please use the hpi i am attaching. I have added some additional logs around the failing area.

it's an area in code in which we ask for the testname via rest and it seems to fail.

regards,

Daniel

This is the console log;

Started by user unknown or anonymous
Building in workspace C:\Jenkins_Home\workspace\Performance Center example job
Mon 07.23.2018 at 01:48:51 PM BST - plugin version is '5.4.3-beta-SNAPSHOT'
Mon 07.23.2018 at 01:48:51 PM BST - Validating parameters before run
Mon 07.23.2018 at 01:48:51 PM BST - OK
Mon 07.23.2018 at 01:48:51 PM BST - Trying to login
[PCServer='xyz', User='abc.123']
Mon 07.23.2018 at 01:48:52 PM BST - Login succeeded
Mon 07.23.2018 at 01:48:52 PM BST - Searching for available Test Instance
Mon 07.23.2018 at 01:48:53 PM BST - Found testInstanceId: 375
Mon 07.23.2018 at 01:48:53 PM BST -
Executing Load Test:
====================
Test ID: 1764
Test Instance ID: 375
Timeslot Duration: 0:30(h:mm)
Post Run Action: Collate Results
Use VUDS: false
====================

Mon 07.23.2018 at 01:49:07 PM BST -
Run started (TestID: 1764, RunID: 1910, TimeslotID: 4007)

Mon 07.23.2018 at 01:49:11 PM BST - Error while trying to get testname. Error: com.microfocus.adm.performancecenter.plugins.common.pcEntities.PcException: executeRequest exception: Operation failed. Error code: 1001
Mon 07.23.2018 at 01:49:11 PM BST - Set HP_RUN_ID Environment Variable to 1910Mon 07.23.2018 at 01:49:12 PM BST - RunID: 1910 - State = Initializing
Mon 07.23.2018 at 01:50:11 PM BST - RunID: 1910 - State = Running
Mon 07.23.2018 at 01:50:34 PM BST - RunID: 1910 - State = Collating Results
Mon 07.23.2018 at 01:50:58 PM BST - RunID: 1910 - State = Before Creating Analysis Data
Mon 07.23.2018 at 01:50:59 PM BST - Logout succeeded
Mon 07.23.2018 at 01:51:00 PM BST - Result Status (PC RunID: 1910): SUCCESS

• - -
  Build step 'Execute performance test using Performance Center' changed build result to SUCCESS
  Recording test results
  Finished: SUCCESS

This is all I can see in the Jenkins.error log;

Jul 23, 2018 1:50:59 PM org.apache.http.client.protocol.ResponseProcessCookies processCookies
WARNING: Invalid cookie header: "Set-Cookie: LWSSO_COOKIE_KEY=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/; httponly". Invalid 'expires' attribute: Thu, 01 Jan 1970 00:00:00 GMT
Jul 23, 2018 1:50:59 PM org.apache.http.client.protocol.ResponseProcessCookies processCookies
WARNING: Invalid cookie header: "Set-Cookie: QCSession=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/; httponly". Invalid 'expires' attribute: Thu, 01 Jan 1970 00:00:00 GMT
Jul 23, 2018 1:51:01 PM hudson.model.Run execute
INFO: Performance Center example job #15 main build action completed: SUCCESS

Jenkins.out shows no events at the time of the build. 

Hi 

I am unable to unzip the latest downloaded "hp-application-automation-tools-plugin.zip" file , getting Unexpected Error "0x80004005: Unspecified error". Tried in both 7Zip and WinZip  

i Umesh,

Try to use winrar (I used it to package and split the archive files). 

Regards,
Daniel

 Thanks Daniel, this time I am able to unzip the file, but still I am getting below exception in Console:

Note: we use checkpoint vpn to connect Performance Center   

Started by user Umesh S G
Building in workspace C:\Program Files (x86)\Jenkins\workspace\My_PC
Wed 07.25.2018 at 05:11:32 PM IST - plugin version is '5.4.3-beta-SNAPSHOT'
Wed 07.25.2018 at 05:11:32 PM IST -
- - -
Test description: PC Integration
Wed 07.25.2018 at 05:11:32 PM IST - Validating parameters before run
Wed 07.25.2018 at 05:11:32 PM IST - OK
Wed 07.25.2018 at 05:11:32 PM IST - Trying to login
[PCServer='http://http://xyz.net:8080/qcbin/', User='abcdef']
Wed 07.25.2018 at 05:11:36 PM IST - Login succeeded
Wed 07.25.2018 at 05:11:36 PM IST - Searching for available Test Instance
Wed 07.25.2018 at 05:11:38 PM IST - getCorrectTestInstanceID failed, reason: com.thoughtworks.xstream.mapper.CannotResolveClassException: html
Wed 07.25.2018 at 05:11:38 PM IST - java.lang.NumberFormatException: null
Wed 07.25.2018 at 05:11:39 PM IST - Logout succeeded
Wed 07.25.2018 at 05:11:39 PM IST - Empty Results
Wed 07.25.2018 at 05:11:39 PM IST - Result Status: FAILURE

Hi Umesh,

Simon had similar error and it was resolved after creating a new Jenkins job from scratch (or using an existing one but define a new PC build step in it after installing the plugin).

I am reviewing the code to see if i can get more informative exception for this getCorrectTestInstanceID .

regards,
Daniel

Hi Daniel,

No luck for me, still I am facing same issue. Few points I just wanted to notify here :

1) Our Performance Center (PC) is hosted in different location and secured network.

2) In order to access that PC hosted in secured network, I have to use Check-Point VPN

Is this secured network is causing the problem ?

Regards

Umesh 

Looks like I appear to have taken a step backwards, I now cannot run any tests. The job shows;

Started by user unknown or anonymous
Building in workspace C:\Jenkins_Home\workspace\get_quote_IF_proxy
Thu 07.26.2018 at 02:45:55 PM BST - plugin version is '5.4.3-beta-SNAPSHOT'
Thu 07.26.2018 at 02:45:55 PM BST - Validating parameters before run
Thu 07.26.2018 at 02:45:55 PM BST - OK
Thu 07.26.2018 at 02:45:55 PM BST - Trying to login
[PCServer='http://bob', User='me.too']
Thu 07.26.2018 at 02:45:56 PM BST - Login succeeded
Thu 07.26.2018 at 02:45:56 PM BST - Searching for available Test Instance
Thu 07.26.2018 at 02:45:56 PM BST - Found testInstanceId: 378
Thu 07.26.2018 at 02:46:01 PM BST - Error: executeRequest exception: Operation failed. Error code: 1001
Thu 07.26.2018 at 02:46:01 PM BST - Error: Run could not start!
Thu 07.26.2018 at 02:46:02 PM BST - Logout succeeded
Thu 07.26.2018 at 02:46:02 PM BST - Empty Results
Thu 07.26.2018 at 02:46:02 PM BST - Result Status: FAILURE

And the error log shows even less;

Jul 26, 2018 2:46:03 PM hudson.model.Run execute
INFO: get_quote_IF_proxy #10 main build action completed: FAILURE

The only difference I can think of is a new Jenkins.war file, I'm currently on 2.121.2

I am able to trigger the same test from a PC REST API request.

I did notice that the REST request needed a TestInstanceID, whereas the plugin is set to Automatically select. However, setting the plugin TestInstanceId to manual and giving it a number didn't make any difference.

Hi Simon, Hi Umesh,

@Umesh, the authentication passes OK but then the first PC REST operation fails (which is getCorrectTestInstanceID). I suggest you verify if the PC user defined in Jenkins job does indeed have enough permissions on the PC project where the test is defined. As for vpn being a possible issue, I don't think so otherwise authentication would have failed (try to set a user with wrong password and you should see an authentication failure).

@Simon, your last logs show indeed a regression as it is a situation that should be handled now. The failure occurs when trying to get the testname and with the last plugin i sent you, it is now ignored and replaced by providing run_id instead of the testname which allows the job to continue forward. I cannot say why the REST API fails to retrieve the testname (perhaps some permission issues or something else, I hope our QA can reproduce this behavior which will allow me to debug because i am not) but this name is used to create, later on, a meaningful link for reports and is not really essential for the execution of the test). Try to download once again the last plugin i uploaded to this case and use it (perhaps there was a confusion between all the plugin i uploaded in this defect report and the previous one). I don't think the version has something to do with this as i am using Jenkins 2.132 (see sreenshot).

Regards,
Daniel

Hi,
Please let me know if you continue facing troubles with this fix.
Just for you to know, a new plugin is now released in Jenkins Plugins marketplace and it takes into considerations the JEP-200 problems. Feel free to download it from there.
regards,
Daniel