Apache JMeter vs. Jenkins

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
JMeter
Score 8.1 out of 10
N/A
JMeter, from Apache, is a load and performance testing tool.N/A
Jenkins
Score 8.3 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.N/A
Pricing
Apache JMeterJenkins
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
JMeterJenkins
Free Trial
NoNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache JMeterJenkins
Considered Both Products
JMeter
Chose Apache JMeter
We found BlazeMeter's service to fit great with our JMeter scripts, since they execute our JMeter scripts and provide excellent reporting tools and graphs, besides multi region and infrastructure to support different configurations of multiple concurrent users. I have used HP …
Chose Apache JMeter
Gomez doesn't have problems like the waiting time for a test to run, a limited number of locations and browser agents, lack of reports, etc. But Gomez is a commercial software and JMeter is not.
Chose Apache JMeter
Both tools are great, but JMeter allows for better performance/load testing, scalability, and is free.
Chose Apache JMeter
I have used LoadRunner and Silkperformer, and so far Jmeter turns out be the easiest to use of all these. While each of them have their own ROI, Jmeter can be picked by anyone in hours and start testing within a day. While with other tools, we need to get license, install them …
Jenkins
Chose Jenkins
We considered using Gitlab, but after some comparing, we found Jenkins was better in every way!
Chose Jenkins
Jenkins and Hudison were originally the same source. I prefer Jenkins. Because it is open source, and has a large community to support. I am not familiar with Bamboo. So nothing to say about that.
Top Pros
Top Cons
Features
Apache JMeterJenkins
Load Testing
Comparison of Load Testing features of Product A and Product B
Apache JMeter
7.6
24 Ratings
10% below category average
Jenkins
-
Ratings
End to end performance management9.021 Ratings00 Ratings
Integrated performance data8.722 Ratings00 Ratings
Deployment model flexibility6.821 Ratings00 Ratings
Real time monitoring8.721 Ratings00 Ratings
Automated anomaly detection5.018 Ratings00 Ratings
Best Alternatives
Apache JMeterJenkins
Small Businesses

No answers on this topic

GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
ReadyAPI
ReadyAPI
Score 8.2 out of 10
GitLab
GitLab
Score 8.9 out of 10
Enterprises
ReadyAPI
ReadyAPI
Score 8.2 out of 10
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache JMeterJenkins
Likelihood to Recommend
8.3
(39 ratings)
8.2
(69 ratings)
Likelihood to Renew
8.6
(12 ratings)
-
(0 ratings)
Usability
9.0
(1 ratings)
5.0
(3 ratings)
Availability
1.0
(1 ratings)
-
(0 ratings)
Performance
8.0
(1 ratings)
8.9
(6 ratings)
Support Rating
10.0
(1 ratings)
6.6
(6 ratings)
Online Training
1.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apache JMeterJenkins
Likelihood to Recommend
Apache
JMeter is well suited for Java applications where the user can script the scenario once and make changes to accommodate for as many numbers of users for load test execution. The image and selection of any files or exporting files scenario is handled well.
It is less appropriate to test Ajax applications where it is required to script click per use.
Read full review
Open Source
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Read full review
Pros
Apache
  • Easy of use - in generate load like HTTP requests, and processing/analyzing the responses. No coding is necessary at the basic level, just need to understand load testing and the infrastructure being tested.
  • Automatic management of things like cookies to help with session state support - so you don't specifically have to worry about it or handle it
  • Lots of testing/configuration options to suit your needs in making the right load generation (sampling requests), and analyzing the results, including any pre and post processing of the results first. Things like the Beanshell/BSF pre/post processors, response assertion, regular expression extractor, XPath extractor, CSV data set config
  • There is a JMeter cloud service called BlazeMeter that I think would be useful for those that need to scale up high load without provisioning their own systems. I've not personally tried it though, but I recently attended a meetup presentation that highlighted nice useful features that BlazeMeter provides. One should evaluate the service if they are considering JMeter and need to expand beyond existing hardware resources.
Read full review
Open Source
  • Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
  • Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
  • Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
Read full review
Cons
Apache
  • Jmeter requires many tweaks with respect to its configuration file and thread properties. users need to edit theses files themselves. There could be some interface where we can edit this fields.
  • Jmeter cannot handle more threads and hangs up when we increase the number of threads. This causes lot of inconvenience. In these situations, user can be notified that such change would be lead to slow performance so that user can do as required. The same appears when we try to view huge files on graph listener.
  • Jmeter should optimize the read and write access to output csv since it acts as overhead to the I/O performance. This affects our test results for the application which we are testing.
Read full review
Open Source
  • The UI could be slightly better, it feels kind of like the 90s, but it works well.
  • An easier way to filter jobs other than views on the dashboard.
  • An easier way to read the console logs when tests do fail.
Read full review
Likelihood to Renew
Apache
Price, Wiki and user sharing. Having access to the information provided by the developers and other open source providers is key for me. The ability to share information and get answers directly is very important to success in software testing. And the price of this product currently is amazing. Too many companies charge way too much money for products that are far behind in their value and pertinence
Read full review
Open Source
No answers on this topic
Usability
Apache
I can jump right into a new test plan and start building from scratch. The natural progression from test plan to thread group and then designing the basic format of the process is very streamlined and smooth. With only slight modifications I can build out a very complex model from a very basic beginning.
Read full review
Open Source
While the day to day use is very easy, the configuration and setting up of the system or new projects can be cumbersome.
Read full review
Performance
Apache
No answers on this topic
Open Source
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Read full review
Support Rating
Apache
I have been using JMeter for the last year. By using this tool, you can make sure the system will work under varied loads. It helps us to simulate real time scenarios by creating required virtual users and make sure the application will work under load. Perform load, stress, and stability testing using JMeter.
Read full review
Open Source
There is a large development community - but it is shifting as people move towards other tools. A lot of companies still use Jenkins and will build propriety tools, which doesn't help any of the open-source community. Jenkins has a lot of help and support online, but other, more modern, alternatives will have better support for newer tech.
Read full review
Alternatives Considered
Apache
I have used LoadRunner and Silkperformer, and so far Jmeter turns out be the easiest to use of all these. While each of them have their own ROI, Jmeter can be picked by anyone in hours and start testing within a day. While with other tools, we need to get license, install them (takes a while) and setup tests and firewalls, etc.
Read full review
Open Source
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
Read full review
Return on Investment
Apache
  • Good ROI on improving the performance of the application.
  • Finding issues in the performance.
  • Benchmark the performance results.
  • CON: Need skillset to create and maintain the scripts in Java.
  • Scripts are reusable and it is executed by any user.
  • Need Client and Server setup to execute the scripts.
Read full review
Open Source
  • Faster Time-to-Market: Jenkins automate the build, testing, and deployment process, enabling faster feedback and continuous improvement.
  • Improved Quality: Jenkins automatically run unit tests and integration tests, ensuring that code changes meet the necessary quality standards.
  • Cost Savings: Jenkins is an open-source tool that is free to use
Read full review
ScreenShots