Hi Dorin,
I see that the error expose from the new HpToolsLauncher was on how the key was searched. Infact it searched the key "almUsername" instead of "almUserName" that the plugin usually looking for.
The output was this one:
C:\jenkins_OS\workspace\ISP-TDNR\ChooseAndLogin\HpToolsLauncher.exe -paramfile props0305202111072587499.txt
"Started..."
Timeout is set to: 3600
Run mode is set to: RUN_LOCAL
Unable to retrieve test set folder: Node not found.
ID = 88181, TestSet = ALM Scenario Sicurezza, TestSetFolder = 02 SEC
ID = 35081, TestSet = ALM Scenario Sicurezza, TestSetFolder = System TDNR
============================================================================
Starting test set execution
Test set name: ALM Scenario Sicurezza, Test set id: 35081
I don't know why it gives me the row that I evidence in Bold but it seems to execute correct testset.
Then I tried to rename the testset in the subfolder and it runs correctly the testset in the correct path.
I tried to run the same propfile but I changed the name of the testset inside the parent path and it give me an error:
C:\jenkins_OS\workspace\ISP-TDNR\ChooseAndLogin\HpToolsLauncher.exe -paramfile props0305202111072587499.txt
"Started..."
Timeout is set to: 3600
Run mode is set to: RUN_LOCAL
Unable to retrieve test set folder: Node not found.
ID = 88181, TestSet = ALM Scenario Sicurezza_4SR, TestSetFolder = 02 SEC
ID = 35081, TestSet = ALM Scenario Sicurezza_L, TestSetFolder = System TDNR
Could not find TestSet ALM Scenario Sicurezza
Null target test set
============================================================================
Starting test set execution
Eccezione non gestita: System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, String testParameters, Double timeout, QcRunMode runMode, String runHost, Boolean isFilterSelected, String filterByName, List`1 filterByStatuses, TestStorageType testStorageType)
in HpToolsLauncher.AlmTestSetsRunner.Run()
in HpToolsLauncher.Launcher.Run()
in HpToolsLauncher.Program.Main(String[] args)
Thank you and best regards,
Massimo.
Can you please try to use the latest plugin (6.8) and check if the issue still exists?