Hello Nick Kolesnikov,

Do you have any updates for this case?

Thank you,

Hilda

Hi Nick Kolesnikov,

Please ignore the first comment from Hilda, because she observed at that time a different behavior, that seemed to be unexpected at the first look.
After a deeper analysis I think that is ok, at least from plugin's point of view, and however, it is not similar with the reported scenario.

So, when you get a chance, please attach here or send by email the requested files (located in the path printed in the Console Output, where appears the call to HpToolsLauncher.exe).

If you need more details please let us know.

Hi Nick Kolesnikov,

Thank you for the quick reply.
After hours of testing I still can't reproduce the issue as described, ... but maybe I'm missing something.
For further investigation, I'd ask for some files and output logs from your side.

As you may know, at the end of build there are some files generated in the Jenkins' workspace folder, for each iteration, having this name pattern:

propsDDMMYYYYHHMMSS###.txt
ResultsDDMMYYYYHHMMSS###.xml

If there were 3 iterations, then 3 props files and 3 results files are generated for that build #. 
The exact name of each props file is also printed in the Console Output, like in this example.

 "C:\Program Files (x86)\Jenkins\workspace\ALM Pipeline Quick\HpToolsLauncher.exe" -paramfile props02082021180608325.txt

1. Please find and provide the props and results files corresponding to one build # that you consider relevant.
  The resultsFilename is printed in the props file.

A props file looks like this:

#
#Mon Aug 02 18:06:08 IDT 2021
runType=Alm
almRunHost=MYD-HVM03172
almTimeout=-1
almDomain=DEFAULT
FilterTests=false
almUsername=sa
almApiKeySecret=********* 
almProject=CI_INTEGRATION
almPassword=**********
TestSet1=Root\\Dorin\\QuickPassFail
almRunMode=RUN_REMOTE
almServerUrl=http\://myd-vm21045.swinfra.net\:8080/qcbin
SSOEnabled=false
resultsFilename=Results02082021180608325.xml

Make sure the almApiKeySecret / almPassword values are masked before sending. 

2. Additionally, please save and provide us the full content of the Console Output, related to that build #.

Thank you in advance.

Sure, Dorin.
{{ The bug itself can be replicated consistently on a big number of test runs, at least >2 }}
-----------------------------
node{

int x1 = SetComp.substring(0,1) as Integer

stage('Build')
Unknown macro: { // echo "$x1" }
stage ('Word-02')

echo 'Word x10-02'
for (i=0; i<x1; i++)

 { runFromAlmBuilder almApiKey}
almApiKey: '<APIKEY>', almClientID: 'CLIENTID', almDomain: '<DOMAIN>', almPassword: 'PASSWORD', almProject: 'PROJECT', almRunHost: 'HOST', almRunMode: 'RUN_REMOTE', almServerName: 'SERVERNAME', almTestSets: '''Root
SI Testing
Unit tests
Word x2''', almRunResultsMode: '', almTimeout: '700', almUserName: 'USERNAME', filterTestsModel: [blockedCheckbox: false, failedCheckbox: false, noRunCheckbox: false, notCompletedCheckbox: false, passedCheckbox: false, testName: ''], isSSOEnabled: false
}

}

}

Hi Nick Kolesnikov,

Can you please provide a groovy script (without sensitive information) which you used in the pipeline in order to reproduce the issue?

Thank you in advance,

Dorin.

Hello,

We are aware of this problem, and the fix will be included in the next plugin release.