jmeter-maven-plugin | The JMeter Maven Plugin | Plugin library

Sounds like you have not configured enough xmx memory for the JMeter process. You can set the amount of memory allocated to the process in the configuration settings for the plugin like this:

It looks you ran your pipeline on self-hosted agent. Or you configured the maven to retrieve the dependencies from the local repository(in mvnsettings.xml, or .m2/settings.xml ). If you ran your pipeline on self-hosted agent. You can check if the local repo /testartifacts/m2repository exists.

If you run your pipeline on cloud agents, you need to find which setting files configured the the local repo, And remove the localRepository.

Then you might need to use Maven Authenticate task to provides credentials for Azure Artifacts feeds and external Maven repositories.

Add Maven Authenticate task at the top of your pipeline. And select your azure maven feed from the Feeds dropdown list

This task will store the credentials on a temp settings.xml file(with feed name as the server id, see below) on the agent, which will be used to authenticate the maven repository in the following maven task.

Noted: The repository id you specified in your pom.xml file(ie. see below highlighted) should be the same with the name of your azure artifacts maven feed. Or it will still fail to authenticate the feed in the follow maven task. for the server id in the temp settings.xml file created above is the feed name.

In order to let someone to access the pods in your k8s cluster you need to expose the IP addresses and RMI ports to the outside world

It will not "include the network time in my perf test response times" because the slaves which are running on pods are doing the real job, the master only collects, aggregates and visualises the test results.

More information on JMeter Properties and ways of setting and overriding them: Apache JMeter Properties Customization Guide

I don't think this is the correct way to enable/disable the thread lifetime setting:

This configuration block:

You will see the error in the View Results Tree listener only if sampler can be executed, if it cannot be executed due to improper JMeter configuration - you should be looking for error messages in jmeter.log file

Also the way you're adding dependencies is not suitable for JMeter Maven Plugin, it uses Eclipse Aether which has different dependencies resolution logic

So you need to change your pom.xml file to look like:

Had to add false Afterwards i added each library needed for the script to run

https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/maven-jmeter-plugin-users/bf_uWS2TqXU

Just put your JMeter Maven Plugin declaration under the jmeter profile like:

Your test didn't execute successfully:

therefore results file is empty therefore JMeter fails to generate the HTML Reporting Dashboard.

Actually a not-properly-handled NPE indicates that a big problem in the code as yoiu shouldn't normally see issues like this in more or less mature software so you can report the issue via JMeter Bugzilla as JMeter shouldn't throw a NPE, it should rather report a human-readable message that the results file is empty suggesting inspecting jmeter.log file for possible reasons.

So you should see your_test_script_name.jmx.log file under target/jmeter/logs folder., I'm pretty much sure that you will find the root cause of your test script failure there.

Check out How to Use the JMeter Maven Plugin article for more information on running JMeter tests via Apache Maven