neotyspluginsupport Can you look into this?
I guess master builds are using a custom settings.xml file: https://ci.jenkins.io/job/Plugins/job/neoload-plugin/job/master/ which PRs dont use and thats why its failing. Can you please help?

Hi abmaster,

A pull request fixing the build issue is open (https://github.com/jenkinsci/neoload-plugin/pull/21).
Once it has been merged could you please update your PR to include this fix ?

neotyspluginsupport Awesome! I will wait for this one to get merged.

neotyspluginsupport The PRs are merged, can you please let me know when we plan to release new plugin version with this bug fix?

Hello abmaster,

Our QA team is currently qualifying the latest build.
A new release will be published as soon as the validation process is OK, but it will take a few days for that.

Hello abmaster,

In order to qualify the fix, could you please provide us the following information:

1. Which OS is running the Jenkins Controller ?
2. Which OS is running the Jenkins agent (Windows if we understand correctly) ?
3. Could you provide an example configuration to reproduce the issue ?

Thanks for your help.

neotyspluginsupport Here are the answers:
1- Controller is Ubuntu20.X
2- Windows 10 agent
3- I am pasting the screenshots :

Variables:

Step using the variables:

Build log

Kindly let me know if you need anymore help.

Honestly I think there a lot of scope for improvement in the plugin as well as the product itself.

Hi abmaster,

Thank you very much for your help.
Version 2.2.11 has just been released, you should be able to install it on your Jenkins server in the coming hours.

neotyspluginsupport happy to contibute.
One more query, in my jenkins, under plugin management, Updates section I still see available version 2.2.10
and not 2.2.11, any way this can be fixed?

Its showing 2.2.11 now, thanks.