I am using jmeter-maven-plugin to execute JMeter tests (JMX Files) as a maven project from Jenkins.
What I observed is:
When rampup time is more or virtual user is more, Jenkins freezes the execution towards the end. It keeps on executing for days if not stopped.
When executed outside Jenkins e.g using maven commands directly using cmd, works great. Also when executed directly from JMeter GUI, works fine.
There was an issue with jmeter maven plugin which was fixed in later version.
Solution was made by Abhishek Swain.
See
Related
I want to run jmeter script parallely through jenkins.
currently i have tried BZM-concurrency thread group and Parallel controller to achive this on my local machine, which is working fine. please help me to run it through jenkins, it get finish with success but script never starts. Do i need any plugins on jenkins to achieve this?
my set is shown below, let me know is there any other way to achieve this.
You need the same plugins in Jenkins master (and all the slave if any) which are used in the test plan, the easiest is just to copy the existing JMeter installation folder to Jenkins instance(s)
Alternatively you can install the required plugins using JMeter Plugins Manager
If your Jenkins doesn't have the GUI - it is possible to install the plugins via the command-line
I am running some performance tests from Jenkins. I do have two Windows machines with JMeter and I can configure from Jenkins which one to use. Everything works as expected here.
My issue: I did create another job for Stop/Shutdown the tests in case something goes wrong and you have a big run time. Whenever I try to summon Stoptest.sh/Shutdown.sh on the Windows machine that run tests, nothing happens.
How can I stop tests remotely? It has anything to do with the listening port? Thank you.
PS: Tests are ran using PSExec from Jenkin's Windows slave so there is no active CMD window on the screen.
Be aware that .sh is extension for Linux shell scripts, they cannot be executed by Windows command-line interpreter (CMD or Powershell) if you're running JMeter on Windows you need to go for shutdown.cmd or stoptest.cmd instead
There is also AutoStop Listener plugin which can be used for conditional stopping of JMeter test basing on various criteria, it can be installed using JMeter Plugins Manager
I've got the following setup:
server 192.168.0.xxx running Jenkins 1.643
server 192.168.0.yyy running SonarQube 5.2 (with Java 1.8.0_66)
server 192.168.0.zzz running PostgreSQL as SonarQube DB (FYI)
I want Jenkins to run a SonarQube analysis on a specific project. I therefore created a job with goal sonar:sonar -Dsonar.host.url=http://192.168.0.yyy. Everything's working well except for code coverage in SonarQube. It says there's a coverage of 0,0 % although there are several tests run by Jenkins.
So I'm pretty sure test results are not published to SonarQube. Google brought me to solutions exporting the results to a directory on the same server and telling SonarQube this directory via -Dsonar.junit.reportsPath.
But this solution is not that easy to implement having Jenkins and SonarQube not on the same server. Long story short: is there another way publishing JUnit test results to SonarQube?
The report path should point to a directory where the analysis is run not on the sonarqube server
So when you are running the sonar:sonar command just use the -Dsonar.junit.reportsPath to point to the the directory containing the report of unit test execution and you should be fine.
Im using Sonar with Sonar Runner and Jenkins.
Strange thing is that when i start the job manually everything works fine but on the periodic nightly builds it fails and says:
org.sonar.runner.RunnerException: No files matching pattern "java" in directory
So i understand that Sonar Runner cant find my source files. But why is that so? I mean when i start it manually Sonar is working fine and using source files. i didn't change anything.
Its the exact same job...
If I generalize your question to "What should I do if my Jenkins job fails at random times after working other times?" one of the first steps I always do is delete the workspace and rerun the build. You can also usually configure the SCM plugin to do a clean checkout of the source rather than an update. That has solved issues for me in the past.
I am using Ant to start/stop our JBoss server in Jenkins. The JBoss server starts fine in Jenkins, but the build never finishes even though the server has started. Is it possible to define in Ant or in Jenkins a way to overcome this? I.e. is it possible in Jenkins to overcome this, or is it possible in Ant to somehow start the server "in background" so that when Jenkins has executed the Ant task it immediately goes to next step in the build (I can manually define a sleep in Jenkins to wait for the server to start)?
Instead of using ant, you could explore JBoss Management Plugin