Answered question

why Executing a Yaml behaves different in CMD and jenkins?

I run this line in cmd NeoLoadCmd.exe -noGUI -project "c:\file.yaml" -launch CatalogueStandard -nlweb -nlwebToken mytokennumber -nlwebProxy http://user:pass@proxy -leaseServer nlweb -leaseLicense 50:1 and runs without error. But when I run the same command from jenkins, the test run but in all page request I get the "NL-NETWORK-01".
In my NeoLoad configuration I use the same proxy for Internet and Application.
In jenkins I also have the same proxy.

Jose Ernesto V.
Jose Ernesto V.

Jose Ernesto V.

Level
0
47 / 100
points
Nouredine A.
Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

NeoLoad stores the proxy information in the user profile so if you run your tests from Jenkins with a different user you may not have the same proxy settings compared when you run it manually from the command line.

In the Jenkins console there's a line indicating where the logs are stored with the user profile name something like that (on LInux)

logging to /root/.neotys/neoload/v6.10/logs as user: root

If we stick to that path example look at the /root/.neotys/neoload/v6.10/conf folder where you have the "controller_user.properties" file that contains your proxy settings. In your case the proxy section might be empty.

You can simply check the same in the user folder used to start your command line that works and copy the "controller_user.properties" to the "Jenkins" user to make sure that they have the same configuration.

Did you find this useful ?

No (0)

Yes (0)

0% of users found this answer useful

Other answers

Jose Ernesto V.
Jose Ernesto V.

Jose Ernesto V.

Level
0
47 / 100
points

hi Nouredine A. thanks for your answer. You are right. In my case with windows the location file is C:\Windows\System32\config\systemprofile\AppData\Roaming\Neotys\NeoLoad\v7.0\conf
Once I put the proxy in the controller_user.properties had runs fine