Difficult to say why getting the test name via rest API fails.

The warnings in the jenkins logs do not seem related (the timing is different: REST API error occuring at 01:49:11 and jenkins warning at 1:50:59).

We use the test name to publish trend report (if the option is selected). In the solution i sent you, i replace it by the run id which will be less meaningful.

I will commit this change and keep the error in the logs so we can have an idea how frequent this error is and if our QA can catch it in their environment.

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