--- title: Jenkins Reviews meta_title: 'Jenkins Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 572 reviews by the users' company size, role or industry to find out how Jenkins works for a business like yours. aggregate_rating: rating_value: 4.4 review_count: 572 scale: '5' date_modified: '2026-08-07' parent_category: name: CI/CD Tools url: https://www.g2.com/categories/ci-cd-tools --- # Jenkins Reviews **Vendor:** The Continuous Delivery Foundation (CDF) **Category:** [Continuous Integration Tools](https://www.g2.com/categories/continuous-integration) **Average Rating:** 4.4/5.0 **Total Reviews:** 572 ## About Jenkins The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project. ## Jenkins Pros & Cons **What users like:** - Users appreciate the **ease of use** of Jenkins, enhancing their development workflow with seamless integration capabilities. (27 reviews) - Users love Jenkins for its **seamless integrations** with various tools, enhancing automation and development efficiency. (20 reviews) - Users appreciate the **extensive plugin ecosystem** of Jenkins, enabling seamless integration with various tools and codebases. (18 reviews) - Users appreciate the **extensive plugin support** in Jenkins, enabling seamless integration with various tools and platforms. (17 reviews) - Users value the **automation capabilities** of Jenkins, appreciating its flexibility, extensive plugins, and scalability for various environments. (14 reviews) - Users value Jenkins for its **automation efficiency** , ensuring smooth continuous integration and delivery processes with extensive support. (13 reviews) - Flexibility (13 reviews) - Easy Integrations (12 reviews) - CD Integration (11 reviews) - Pipeline Management (11 reviews) **What users dislike:** - Users often face **plugin issues** in Jenkins, including compatibility problems and high memory consumption with multiple plugins. (16 reviews) - Users find the **confusing interface** of Jenkins outdated, making setup and management of pipelines a challenge. (12 reviews) - Users find the **difficult setup** of Jenkins cumbersome, requiring significant time for configurations and plugin management. (9 reviews) - Users find Jenkins' **user interface outdated** , which complicates usability and overall experience. (9 reviews) - Users find Jenkins' **complexity** in setup and management a significant hurdle, impacting usability and efficiency. (8 reviews) - Users experience **complex setup** challenges with Jenkins, particularly due to the intricate configuration and plugin management. (8 reviews) - Performance Issues (8 reviews) - Users find the **UI outdated** and complex, making setup and management challenging, especially for newcomers. (8 reviews) - Update Issues (7 reviews) - Difficult Management (6 reviews) ## Jenkins Reviews ### 1. Good CI tool, lots of plugins for enhancement **Rating:** 4.5/5.0 stars **Reviewed by:** Tonya E. | Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** June 28, 2016 **What do you like best about Jenkins?** Jenkins is pretty easy and straightforward to install and get setup. There are also lots of plugins that you can use to enhance your experience. I've used the git, gitlab and svn plugins. I also like that the interface is simple and easy to navigate. I also like the email notifications. **What do you dislike about Jenkins?** Overall, I don't have any major complaints. For multi-module or larger projects, sometimes the build can get out of order. Maybe this is due to human error - but one build kicks off another ...one fails .. but then you have to wait for other builds to catch up before you have a successful build. **What problems is Jenkins solving and how is that benefiting you?** You have multiple developers committing code and you need to continuously integrate that code and determine if there are any bugs or errors in the build. It is better to catch these problems sooner than later. ### 2. Jenkins - An open Source awesome tool **Rating:** 5.0/5.0 stars **Reviewed by:** RISHANT A. | Software Engineer & Technical Lead, Telecommunications, Enterprise (> 1000 emp.) **Reviewed Date:** May 23, 2016 **What do you like best about Jenkins?** 1. Its web -based UI makes it platform independent. you can access it from anywhere . FRom your phone , laptop , just anything . It is usually a big problem with many softwares. 2. It comes with a wide variety of plugins . there are plugins to do anything and everything. For any need of yours just download a required plugin and you are good to go. No need to fiddle with code for doing trivial things . It saves lot of your development time . 3. It comes with a lot of security features. Making user management very easy. It has all different kinds of options for user management and Access Control . Very nicely made , this is a very good piece of software . 4. It has a very large community which supports it . **What do you dislike about Jenkins?** I dont like its UI that much . There is a need to improve it . Although , it serves the purpose very well . **Recommendations to others considering Jenkins:** GO for it !! Its amazing . **What problems is Jenkins solving and how is that benefiting you?** I run a company which requires a large number of softwares to run and those softwares keep on updating frequently. It a pain to do their deployment manually every time. Also , there are chances of human error to happen . So, I use Jenkins here. I have automated the whole process and now it all happens automatically every time code is pushed to the repo. It also generates reports for itself. ### 3. Powerful and flexible **Rating:** 5.0/5.0 stars **Reviewed by:** Judy (Morgan) L. | Software Architect, Mid-Market (51-1000 emp.) **Reviewed Date:** July 19, 2016 **What do you like best about Jenkins?** The best is the worst, it is completely configurable and can do whatever you tell it to, if you can figure out how! There's a plug-in for everything. **What do you dislike about Jenkins?** Sometimes the documentation for various plug-ins are a bit brief and it can take some trial and error to get them to work. **Recommendations to others considering Jenkins:** You really need someone with time to learn how to use all of the powerful features and to make sure things keep running smoothly. You will spend a lot of time up front getting things going, but the payoff can be huge. **What problems is Jenkins solving and how is that benefiting you?** We're doing continuous integration and automated test. We have jobs that pull our code from GIT, run unit tests, SQL tests, and Selenium GUI tests automatically. ### 4. Continuous Integration Automation **Rating:** 5.0/5.0 stars **Reviewed by:** Leo W. | Software Developer Engineer, Architecture & Planning, Small-Business (50 or fewer emp.) **Reviewed Date:** November 09, 2016 **What do you like best about Jenkins?** Automated build and deployment of code once checked into a source control. **What do you dislike about Jenkins?** As a tradeoff for flexibility, it can be complicated to setup. Users not intimate with the setup are left with a black box view of build servers. **What problems is Jenkins solving and how is that benefiting you?** Continuous Integration is always a perk when developing software as you can see any problems arise in almost real time. ### 5. We use Jenkins heavily, for builds, deployments, and datacenter management. **Rating:** 4.0/5.0 stars **Reviewed by:** Peter R. G. | Service Management Engineer, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** May 04, 2016 **What do you like best about Jenkins?** I like that it is open, free, and has many plugins, which are also free. **What do you dislike about Jenkins?** The interface is clunky, and sometimes difficult to use. It is especially difficult to manage the output consoles when there are many of them. The auto refresh is not modern and requires a page refresh, instead of any local dynamic updates. **Recommendations to others considering Jenkins:** Jenkins is an excellent free, lightweight script execution platform. Builds, tests, CI, and many other functions are native to Jenkins and can be performed no better with any other software. For highly dynamic content, persistent jobs, etc, I would recommend seeking another solution. **What problems is Jenkins solving and how is that benefiting you?** We perform everything from maven, gradle, chocolatey, rpm, and custom puppet package builds, to large-scale whole product deployments to multiple datacenters in minutes; other uses include jobs to detect load and respond with resource increase or decrease. Finally, we output data to graphs, pulled and built by Jenkins, on Confluence wiki for weekly metrics and performance review. ### 6. Works exactly as expected **Rating:** 4.0/5.0 stars **Reviewed by:** Mitchell B. | Vice President, Investment Management, Mid-Market (51-1000 emp.) **Reviewed Date:** April 25, 2016 **What do you like best about Jenkins?** There are configurations for everything in Jenkins. Every time you need a new build for a new git repo, you can set it to the default and let it run its course, or you can configure every small detail and step to do everything you want. Do you need it to do something after the build is complete, just set it it to run a script after its done, and you are good to go. Everything in Jenkins is configurable and that is its strongest suit. **What do you dislike about Jenkins?** The positive with Jenkins is also a negative in that everything is configurable. In a way, its great, but at the same time, when something goes wrong, you have to look at the configs and read every line since issues are not always logical and easy to find. **Recommendations to others considering Jenkins:** Tenacity and Jenkins are both very similar in design and in quality. You cannot really go wrong with either one and you will not be disappointed either way as well. **What problems is Jenkins solving and how is that benefiting you?** We have a large amount of git repositories that are constantly being changed. We use Jenkins to ensure that each git repository is fully working and is buildable. We then use it to upload the results to Nexus automatically so we have production and QA versions of our code in jar form. ### 7. Automating Android builds with Jenkins **Rating:** 3.5/5.0 stars **Reviewed by:** Paweł G. | Android Developer, Marketing and Advertising, Mid-Market (51-1000 emp.) **Reviewed Date:** April 15, 2016 **What do you like best about Jenkins?** Jenkins is open source and totally free (for commercial use as well) and it is a good reason to use it. It is a popular software with large community so we don't need to worry about support. Many teams begin their Continuous Integration with Jenkins and after a while move to another (paid) build system. **What do you dislike about Jenkins?** I don't like user experience of Jenkins. It doesn't follow latest design trends, but it's not awful at all. Other build systems like TeamCity or Travis are much nicer and intuitive. Jenkins unlike other build systems is not hosted and we need to install it on our own machines (however, it might become an advantage as well). **Recommendations to others considering Jenkins:** You should take Jenkins into consideration as it costs nothing (omitting the time needed to learn it). Other build systems are generally expensive for commercial use, but often worth paying for nicer UX, intuitiveness and better analysis. **What problems is Jenkins solving and how is that benefiting you?** I use Jenkins for Android builds automation followed by Continuous Delivery. Jenkins meets all my needs. We can find plugins for git, gradle and android without the need to write redundant scripts. Moreover, there is a cool Build Monitor plugin that looks really nice when we launch it on external monitor visible to all team members. ### 8. Free, mature and easy to configure **Rating:** 4.0/5.0 stars **Reviewed by:** Babur D. | Senior Java Developer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** April 14, 2016 **What do you like best about Jenkins?** no costs for installing it. Used in every project that I was involved in within my past 5 years of experience. Has a lot of features and easy customisable. Provides reports, graphical representation of current status of running jobs, keeps history of and logs. Has a possibility to configure access rights for users. **What do you dislike about Jenkins?** It could be much more comfortable. I've also tried Atlassian Bamboo which had more advanced features. But because it was years ago I can't recall all benefits of it and would not be able to compare them. **What problems is Jenkins solving and how is that benefiting you?** we use it for: 1) Feature branch build which are triggered on each push to git repo. 2) Nightly builds that are triggered for master/develop branch. 3) As automatic unit tests and integration tests runner. Getting a report about failing tests. 4) We empowered CI server to do daily deployment on DEV server and manually triggering to deploy on QA, TEST and PROD servers. 5) There are also some work is done to do automatic load testing, but I haven't go deep into it. 6) One CI server is used to manage multiple projects. Having all these, the main points are that we have eased deployment process, automatic tests. ### 9. Excellent product - easy to learn & configure! **Rating:** 4.5/5.0 stars **Reviewed by:** Tyler B. | Web Software Developer, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** April 07, 2016 **What do you like best about Jenkins?** There was no learning curve with Jenkins. I've had some experience setting it up, and I've been using it as a developer for years, and it never takes long to figure out how to do something. Creating new builds is easy; Deploying existing builds is as easy as one click; and perhaps most importantly, debugging builds is easy. Whenever a build is broken, it's just a matter of reading the logs or running the build config script inside my local environment. Sometimes I may need to log into Jenkins to see if there's something wrong with the Jenkins host, but that is rarely the case. **What do you dislike about Jenkins?** The web-based user interface feels kind of dated at times, but works fine. It would be nice if there were fewer fields for the default use cases, because it can be bothersome to sift through all the fields to find common variables like Ruby version and destination host name. **Recommendations to others considering Jenkins:** Would definitely recommend to any large team that needs continuous integration. **What problems is Jenkins solving and how is that benefiting you?** Jenkins helps us integrate our code in the form of various builds that we keep running at any given time. it also provides hook-ins to Slack and other chat programs so we can be notified of changes to a build. ### 10. Review of Jenkins CI **Rating:** 3.0/5.0 stars **Reviewed by:** Csaba K. | Android developer, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Jenkins?** I like the Jenkins ecosystem. It has basically plugins for everything, any service can be integrated with Jenkins. Writing new plugins is pretty straightforward as well. Also it is great that we can self-host the Jenkins instance, and install it pretty easily. The slaves are also very easy to add, so one can scale the CI as the resources allow it. **What do you dislike about Jenkins?** The product seems like it stuck in the mid 2000s, the GUI is totally outdated. Configuring the job in the UI sometimes can be tedious, a text-based configuration file can be more help. There is an initiative to support this, with the Jenkins Pipeline plugin. **Recommendations to others considering Jenkins:** I would recommend Jenkins, because all the CI problems can be solved with it, and the new Jenkins 2.0 version will be even better. **What problems is Jenkins solving and how is that benefiting you?** We use Jenkins for pretty much everything. We build and test every merge request in the company, so the code reviewer can immediately see the compilation/static analysis/test results etc. We also use it for continuous delivery, as we deploy user test releases with Jenkins, sometimes manually, sometimes in nightly builds. ### 11. A Must tool for Continuous Integration **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** October 31, 2016 **What do you like best about Jenkins?** There are some tools like (Staf, Make, Scons, etc) which every developer use at some point in their entire development cycle. Jenkins is definitely one of them. I like the following features in 'Jenkins'. - Almost Zero effort needed for initial setup. - Ease of use for all the features - Reporting - Emailing system - Integration with different version repositories **What do you dislike about Jenkins?** Jenkins is a part of our 'Continuous Integration' process. It does its job and delivers everything that is promised. There is actually nothing that I don't like. **What problems is Jenkins solving and how is that benefiting you?** Just one word. 'Continuous Integration'. Jenkins is the best simple tool for 'CI'. Easy to setup and helps to run the different test suites as soon as we submit the code. Saves a lot of time. ### 12. Excellent - easy configuration **Rating:** 4.0/5.0 stars **Reviewed by:** Aniruddha B. | Module Lead, Enterprise (> 1000 emp.) **Reviewed Date:** June 23, 2016 **What do you like best about Jenkins?** * Easy to configure/ set up. * Creating and deploying builds is easy in the interface. * No installation costs **What do you dislike about Jenkins?** * Jenkins webapp is clunky and outdated. * Not enough documentation. Configuration issues resolution can be tough sometimes. * Initial setup time can be high if configuration is not properly done. **Recommendations to others considering Jenkins:** * The product is useful with its build features and easy configuration setup. * Learn the work flow structure and stay ahead of the game. **What problems is Jenkins solving and how is that benefiting you?** * Single CI server to manage multiple projects * Build triggers after every code commit * Test suite run after every code commit. Getting a report for the same. ### 13. Jenkins with Mobile App Build and DIstrubtion Review **Rating:** 3.5/5.0 stars **Reviewed by:** Icyleaf W. | Senior Manager of Mobile Development, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Jenkins?** one click install, has many plugins to use **What do you dislike about Jenkins?** First of all, All download (include jenkins self and plugins) is slow in china, may be sometimes the net gateway is unkonwn or down. second, UI is too ugly. may be learn from travis ci. **What problems is Jenkins solving and how is that benefiting you?** Our testers and products has no idea with how to build a app and how to install it fast(special to ios app), jenkins helps us to solved this problem, i setted up jenkins with configurations, built a backend web site for managing app(upload/download/edit etc). all people is happy. ### 14. Great build tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** August 27, 2016 **What do you like best about Jenkins?** Great build tool for Java applications. Plenty of addons that allow you to build and deploy your applications in the way you need. Good for continuous integration/deployment. The new version of Jenkins (2.x) is a big improvement and the build pipeline is much better. Integration with source control (SVN, Git etc) is great. Integration with other tools (Hipchat, slack, Sonar) etc is fantastic. **What do you dislike about Jenkins?** Updates can sometime break older extensions. Even minor releases will break things. I feel the CI/CD still isn't where it needs to be. It's still feels a bit clunky. **Recommendations to others considering Jenkins:** It's the leader out there. But there are other up and comers that are eating into it's lead. The one downside is that you have to host it somewhere. If you want to be completely cloud based, Jenkins might not work as well. **What problems is Jenkins solving and how is that benefiting you?** A reliable way to build/deploy applications in a consistent reproducible way. ### 15. Jenkins, the easiest way to start with automation workflows and continuous integration **Rating:** 4.5/5.0 stars **Reviewed by:** Michelangelo v. | CEO, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** March 16, 2016 **What do you like best about Jenkins?** Jenkins provides out of the box a complete Continuous Integration system that allows you to automate your development processes within a few minutes. Using it's plugin system, there's basically nothing you cannot automate. When a single instance is not sufficient anymore, Jenkins is easily scalable and fast processing your workflows in parallel. Jenkins offers a great dashboard to manage and display your running processes and even provides additional plugins to have key performance indicators (KPI) displayed on full screen in the offices so there's always transparency with the development teams. Jenkins integrates with the majority of commincation tools, we have for example it integrated into our emails, Slack, IRC channels, SMS Service and Time Tracker so that developers don't have to worry they miss an important update or failure notification. **What do you dislike about Jenkins?** Sometimes you receive failed process stack traces that doesn't show clearly if the failure occured because something failed in Jenkins or in your application workflow. Because Jenkins needs to be installed on-premise and is Java based there's a requirement to have a Java stack available just to run Jenkins. This can sometimes be an issue if you're not having a Java oriented operation as this adds additional support requirements. **Recommendations to others considering Jenkins:** Jenkins offers a huge amount of functionality and it's easy to get lost in the overflow of options. My advise is to start small and automate pushing your local code onto production. Once you understand what it can do more, you can add more processes to this workflow and make them dependend of each other by building pipelines. Once you feel comfortable using Jenkins, you can unleash it's real power and add all testing and QA processes in the mix, have conditional database provisionings and automate provisioning of cloud VM's. Once you start automating your development workflows and move towards continuous deployment, you will see you're saving a lot of precious time that can be reinvested into your development. **What problems is Jenkins solving and how is that benefiting you?** Jenkins is a Continuous Integration system that allows you to automate workflows beyond development so developers have more time to focus on what they do best: development. By implementing Jenkins and a test driven development policy, we have reduced the development overhead by 400% and with the automated processes after development we have our changes pushed to production with less failures and higher quality. ### 16. CC Jenkins Review **Rating:** 4.0/5.0 stars **Reviewed by:** Bill B. | IT Director, Education Management, Mid-Market (51-1000 emp.) **Reviewed Date:** July 13, 2016 **What do you like best about Jenkins?** Jenkins automates time-consuming menial tasks to free up developers to continue writing code. It is integral to our software process flow. **What do you dislike about Jenkins?** I find nothing to dislike. Jenkins is reliable and dependable. Every once in a 'blue moon' it does hang up but I suspect that has more to do with the server it resides on than the actual software itself. **Recommendations to others considering Jenkins:** Use it. Keep your developers doing what they do best. **What problems is Jenkins solving and how is that benefiting you?** Automate menial tasks including unit tests, test environment build, and final deployment of code changes. ### 17. Jenkins is useful for prod deployments **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** March 10, 2017 **What do you like best about Jenkins?** Easy to use interface within team. Code check in is an easy process **What do you dislike about Jenkins?** I have used limited functionalities with in Jenkins for build purpose, Not too sure as still exploring on other features. **What problems is Jenkins solving and how is that benefiting you?** Code check ins, deployment and code merge process ### 18. Really good product **Rating:** 4.5/5.0 stars **Reviewed by:** Jonatan Ezequiel S. | Android Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** April 12, 2016 **What do you like best about Jenkins?** What I most like from Jenkins is the plugin management system. There are a lot of plugins for diferent build types that can be added to Jenkins. It's fully configurable, that's good and bad in fact. **What do you dislike about Jenkins?** Jenkins is fully configurable, so starting a Jenkins server requires that you have a minimum knowledge of a server and how to perform a deploy. If you want something more faster Jenkins is not the option. **Recommendations to others considering Jenkins:** If you want to deliver a project to a CI without configuration dealing Jenkins it's not correct for you. **What problems is Jenkins solving and how is that benefiting you?** I work as Software Enginneer so I daily have to deal with Jenkins. In my case the benefits of Jenkins are around of build automation and running test automation, performing builds and deploys in different development stages. ### 19. Your friend, if you are a hacker **Rating:** 2.0/5.0 stars **Reviewed by:** Amir S. | Software Developer, Mining & Metals, Mid-Market (51-1000 emp.) **Reviewed Date:** May 18, 2016 **What do you like best about Jenkins?** The power of jenkins is in configurations. Everything could be configured which is a pretty exciting feature for a true hacker. **What do you dislike about Jenkins?** The downside of configuring everything is you have to know every single detail. As your configurations become more complex, it is becoming harder and harder to find the root cause if possible issues. **Recommendations to others considering Jenkins:** Dont just start use it. Know what your requirements are, if other simple CI tools does not work for you, then start using it. **What problems is Jenkins solving and how is that benefiting you?** For complex build systems and enterprise environment, jenkins would be a perfect fit. In those cases, simple build systems and test runners would not work for you as you need more flexibility. ### 20. Very flexible and customizable CI software **Rating:** 4.5/5.0 stars **Reviewed by:** Anderson G. | Full Stack Developer, Small-Business (50 or fewer emp.) **Reviewed Date:** May 23, 2016 **What do you like best about Jenkins?** I started looking into Jenkins the first time because it is free. But after being using it for more than 2 years I certainly see others great advantages. It has a lot of plugins which you can install according to your needs. **What do you dislike about Jenkins?** Its interface has an old style and is a little bit heavy. But it doesn't affect the performance of the jobs you execute there. **Recommendations to others considering Jenkins:** Keep it updated and use as less as possible plugins. They are great, but only install what you really needs. **What problems is Jenkins solving and how is that benefiting you?** I'm using it as a platform for our deploy server, where we build our packages, publish and run backup tasks. ### 21. A Good Old Continuous Integration Software **Rating:** 5.0/5.0 stars **Reviewed by:** Gaël R. | Small-Business (50 or fewer emp.) **Reviewed Date:** February 23, 2016 **What do you like best about Jenkins?** Jenkins allows you to do absolutely everything. If a technology JUST came out, maybe no Jenkins plugin is available yet. You could write one, it's not hard, but you can also just use shell scripts, and do absolutely everything from there. It's easy to setup, supports everything you could need and just works. You can even customize it's appearance to match your company's branding, or to update it's oldish look, if you want. **What do you dislike about Jenkins?** Sometimes it feels old. Not so long ago the entire interface was built with HTML tables, like in the 90s. Even if you can customize it however you want, even if the interface has been worked on, it still looks like old. Nobody cares you might say, it's just a CI. It still made me switch multiple times to other CIs like Atlassian Bamboo. However, I always switched back to Jenkins after a few days. I like things to look good, like Atlassian Bamboo, and in the end you are able to make it look good. **Recommendations to others considering Jenkins:** Jenkins looks older than all other solutions. It's because it is. It has much more plugins, supports much more technologies. You can be sure it can achieve what you want to achieve. **What problems is Jenkins solving and how is that benefiting you?** When I was working a lot on OSS projects, I was commit-pushing without testing too much. Jenkins always reminded me when something didn't actually compile, some test broke or some other problem appeared. It also stores builds of every single versions, because I want to. It's a great way to give users access to builds directly. ### 22. One of the best tool for build automation **Rating:** 4.0/5.0 stars **Reviewed by:** Arif K. | Software Developer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** April 13, 2016 **What do you like best about Jenkins?** Best things i like about Jenkins 1. All the project builds are at one place 2. A dashobard to show that which builds are passed and failed 3. Easily integrate with sonar and show testing coverage as a graph. **What do you dislike about Jenkins?** I dont know where to find the latest build. I have to go to the console output to see the download link. If there is a button on dashboard to download the latest build then it will be pretty handy **What problems is Jenkins solving and how is that benefiting you?** We have multiple projects running parallely. Some projects depend on each other. Initially it was quite hard to find the dependent builds of another project and then use it for your own but now you have all at one place. ### 23. Great With Multi-platform projects **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Consumer Services | Mid-Market (51-1000 emp.) **Reviewed Date:** June 23, 2016 **What do you like best about Jenkins?** 1) Ease of build configuration 2) Master/Slave - allowing different platforms to be integrated within a single build system 3) Stability - The automation system is fairly stable 4) Ability to backup the jenkins configuration **What do you dislike about Jenkins?** 1) It lacks granularity: for example, it's not possible to check build success or failure at different levels i.e., basic compilation vs unit tests. It's all or nothing. 2) Parallel jobs step on each other when not properly configured. **Recommendations to others considering Jenkins:** Please try to keep your projects independent and avoid stepping on each other. Also, it's good to update plugins constantly over the time. **What problems is Jenkins solving and how is that benefiting you?** 1) Continuous integration between various teams 2) Smoke builds to identify failures almost instantaneously 3) Plugin integration to allow various code quality controls ### 24. Good tool for continuous delivery, but a little old school **Rating:** 2.0/5.0 stars **Reviewed by:** Evandro S. | Engineering Manager, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** December 28, 2016 **What do you like best about Jenkins?** The easiest way to put jenkins in production. **What do you dislike about Jenkins?** I need a plug-in for everything. Jenkins v1 don't have a native pipeline deployment. **What problems is Jenkins solving and how is that benefiting you?** Build, deploy and test automation ### 25. Jenkins for software builds and test automation **Rating:** 4.5/5.0 stars **Reviewed by:** Derek R. | Sr Member Technical Staff, Consumer Services, Mid-Market (51-1000 emp.) **Reviewed Date:** June 28, 2016 **What do you like best about Jenkins?** Ease of use the web-interface. Basic value provided by the product of automating jobs. The JSON API exposed by Jenkins is also useful. **What do you dislike about Jenkins?** Managing multi-part jobs can be a bit confusing. Also, the UI can get bit cluttered when there are many jobs. **Recommendations to others considering Jenkins:** Jenkins is the Honda of build automation software. It is reliable, consistent, and easy to use. **What problems is Jenkins solving and how is that benefiting you?** Using Jenkins to automate software builds, run unit tests, and provide feedback to developers when the builds have broken. ### 26. Free, Simple and Fun **Rating:** 3.0/5.0 stars **Reviewed by:** Verified User in Internet | Small-Business (50 or fewer emp.) **Reviewed Date:** April 14, 2016 **What do you like best about Jenkins?** I start playing Jenkins just about a week ago because my new job doesn't have any CI yet. I tried Jenkins as it is free and a spare mac mini computer is available. I like the setup of Jenkins, it is extremely easy. I just follow the guide google from internet and no serious problem at all. Up to now, there are about 20jobs running and it works great. Another reason I like it is it is completely my computer. I can install what I need. **What do you dislike about Jenkins?** What I don't like first is the GUI, it looks old style but it just works. I also don't like I have to maintain one more computer as this is a computer just setup by me. I have to worry about if this computer crashes or some other issues occur. **What problems is Jenkins solving and how is that benefiting you?** I set it up because it wants to some robot to help me build my apps (iOS and android) for every code update. It is tedious to build manually each time on my development machine. I saved lots of time and the build delivered more frequent which make the development process smoother and QA can give feed back as quick as possible. ### 27. Really straightforward & easy to setup **Rating:** 4.5/5.0 stars **Reviewed by:** Guillaume A. | Full stack Scala developer, Internet, Small-Business (50 or fewer emp.) **Reviewed Date:** April 14, 2016 **What do you like best about Jenkins?** Jenkins is a free product and can be setup very easily and you can make it running within an hour ! It's really simple to set it up , set up all your projects and customise the settings for your needs ! I really like the fact that I can customise the job as I want . **What do you dislike about Jenkins?** Very slow when you have lot of projects. Jenkins is really big, it's really to get lost in the settings. **Recommendations to others considering Jenkins:** It's really worth using Jenkins. It's free, simple to use and have an instance running and really easy to setup, easy to customise. For a free product, Jenkins it will bring you lot of values. **What problems is Jenkins solving and how is that benefiting you?** Be able to run the tests every time a commit is done on a branch, to verify if there is a bug in the current commit. It's possible to write a script, attached a hook to catch a commit and run the script to execute what I desire. (tests, coverage.....) ### 28. Endlessly configurable and a bit hard to learn. **Rating:** 3.0/5.0 stars **Reviewed by:** Tomáš H. | Freelance Web Developer/Architect/Consultant, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** June 26, 2016 **What do you like best about Jenkins?** Very configurable, can be run on your own machine for free **What do you dislike about Jenkins?** Harder to get up and running compared to populat SaaS solutions **Recommendations to others considering Jenkins:** Double check if it's worth the effort, you might be better of using some SaaS solution instead, if you are not too big. **What problems is Jenkins solving and how is that benefiting you?** We used Heroku to deploy our web projects, but we wanted our own servers. We've switched to Jenkins, and then we were able to realize some savings in cloud bills, but on the other hand we spent a lot of effort to setup and maintain the solution. I guess for a company of 30-50 people, Jenkins is a bit of an overkill. ### 29. Fantastic CI Solution for On-Premise and the Cloud **Rating:** 4.5/5.0 stars **Reviewed by:** Curtis R. | Solutions Architect, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** April 02, 2016 **What do you like best about Jenkins?** The best thing about Jenkins is its ease of use and the broad availability of plugins. The system connects to virtually anything out there today and can operate phenomenally integrating with both on-premise and cloud resources like AWS (I used it for Elastic Beanstalk in particular). **What do you dislike about Jenkins?** The interface is absolutely terrible. They are supposedly working on an improved version at CloudBees, but until then, it definitely looks like an admin tool written by admins; spartan. **Recommendations to others considering Jenkins:** Take the time to plan out your permissions models and install the roles strategy plugin from the get go. Enable SSO via an SSO provider on-premise or in the cloud (Okta works well wth the SAML plugin), install the folders plugin to help organize your projects and then explore the Promoted Builds plugin. Depending on where you're planning on deploying too, there may be plugins to help, such as the AWSEB Deployment plugin. **What problems is Jenkins solving and how is that benefiting you?** I needed a solution that would allow for us to build applications based on specific code branches, perform unit tests, code coverage and security scans, UX tests, initiate penetration tests for specific tiers and deploy the applications to both on-premise and cloud environments. All of these were possible with Jenkins with little to no advanced knowledge all using out of the box functionality. This allowed my teams to go from performing most of these steps manually to performing them in a completely automated state within a matter of days. ### 30. Automatic upload release On Dropbox using jenkins **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** May 24, 2016 **What do you like best about Jenkins?** Automatic upload release on Dropbox using Jenkins. It is easy to automate and self-hosted continuous integration service. It's open source, good community. We can easy to run multiple build simultaneous. **What do you dislike about Jenkins?** We would like to run tests in each build in parallel, but this has proven to be not possible with the current arrangement on the Cloud-bees Jenkins host. **What problems is Jenkins solving and how is that benefiting you?** We are using Jenkins in continues integration system for automatic creating and deploying build as well as running automation on newly created build and Automatic upload release on Dropbox. ### 31. Nice Build and Integration **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** April 15, 2016 **What do you like best about Jenkins?** Build Automation and Continuous Integration. **What do you dislike about Jenkins?** Too more configuration, not easy for me to try. But if you have succeed once, the following is easy to replay. **Recommendations to others considering Jenkins:** For who handles more than 20 machines, you should try it. **What problems is Jenkins solving and how is that benefiting you?** I am a backend engineer. We use Jenkins for Build Automation and Continuous Integration. Our group design and build a large-scale recommendation system engine for billions of clients, on a truly unprecedented scale. Managing such incredible amounts of data and traffic requires unconventional thinking and coming up with lightning fast solutions in real time. We redesign the storage, network, and our cache system, analyzing and improving efficiency, scalability, and stability of the recommendation infrastructure and our data analyzing process. Our objective is optimize the number of connections, throughput, latency, QPS, and, the efficiency and correctness of recommendation algorithms, by all means. ### 32. Enables project management to feel apart of software development cycle **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** December 25, 2016 **What do you like best about Jenkins?** Integrates into any programming language gives full unix bash capabilities **What do you dislike about Jenkins?** It's over complicated and hard. It has too many features and hard to get started **Recommendations to others considering Jenkins:** Give it a try it's a great model it's a great continuous integration tool **What problems is Jenkins solving and how is that benefiting you?** Insuring that software releases are always passing tests and aren't broken ### 33. Free, powerful and easy to configure **Rating:** 5.0/5.0 stars **Reviewed by:** Antonino Francesco M. | iOS Software Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** May 19, 2016 **What do you like best about Jenkins?** no costs for installing it. Creating new builds is easy, i didn't took much in order to figure out how to do something. **What do you dislike about Jenkins?** the GUI is totally outdated, but you could use external CSS/JS in order to have a better GUI. Jenkins unlike other build systems (Bamboo,TeamCity) is not hosted and you have to install into your own machines. Could be painful when you update some plugins and some functionality broke up. **What problems is Jenkins solving and how is that benefiting you?** We use Jenkins in order to deploy automatically our web sites/application ### 34. DevOps Engineer at Refinery29 **Rating:** 3.0/5.0 stars **Reviewed by:** Verified User in Internet | Mid-Market (51-1000 emp.) **Reviewed Date:** December 17, 2015 **What do you like best about Jenkins?** Jenkins is tested, well-known system with a decent ecosystem of plugins and support. **What do you dislike about Jenkins?** Markup. All the configuration is stored in XML, which imho is overkill for what Jenkins does. It also makes version control awkward. I really wish I could use git to keep track of versions of jobs and also as deployment method. Linux sys admins tend to live on the command line, but you can't do that with Jenkins because it forces you to use the other thing that Jenkins has with bad Markup—its gui—bad css, and bad AJAX. I feel like I'm using a system built with '90s web tech by people who don't know much about web design. That opinion is certainly an artifact of my history as a full stack engineer. **Recommendations to others considering Jenkins:** It's good at what it does, but once you scale up and have dozens, if not hundreds, of jobs, maintaining Jenkins can be a bitch. Travis is a good alternative for build jobs, I've heard good things about CircleCI, and GoCD was alright, though CircleCI is a sass offering, and GoCD suffers the same ills that Jenkins does when it comes to version control. For now, Jenkins is likely best in class, but I would love to see an alternative. **What problems is Jenkins solving and how is that benefiting you?** I've always used Jenkins whenever we need an interface to keep track of, and run, jobs. ### 35. Meh but needed **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Higher Education | Enterprise (> 1000 emp.) **Reviewed Date:** June 27, 2016 **What do you like best about Jenkins?** Numerous plugins, fairly easy to set up, does it's job well **What do you dislike about Jenkins?** Not always trivial to solve a Jenkins problem as the error messages aren't always clear. Certain aspects are very rigid **Recommendations to others considering Jenkins:** It may be a hassle to get a job working just right, but in the end the automation is worth it and Jenkins usually offers just enough features to get the job running correctly. **What problems is Jenkins solving and how is that benefiting you?** We are solving the problem of being able to do a light amount of internal testing before sending off our product to QA, in order to minimize the amount of potential issues. ### 36. Great CI, CD but requires setup **Rating:** 3.0/5.0 stars **Reviewed by:** Verified User in Retail | Enterprise (> 1000 emp.) **Reviewed Date:** May 04, 2016 **What do you like best about Jenkins?** There seem to be endless plugins that can be added to Jenkins and it suits all of my needs. Jenkins does a good job of viewing all of your jobs and the customizing of these views is a great feature. **What do you dislike about Jenkins?** As we move to a cloud architecture we would like to see Jenkins setup minimized. Ideally we would like to stand up a Jenkins pipeline in a few minutes rather than an entire day of plugin installs and configuration. **Recommendations to others considering Jenkins:** Faster up time or the ability for wrapping jenkins in docker and configuration/plugins installed will be held. **What problems is Jenkins solving and how is that benefiting you?** We have been using Jenkins to satisfy continuous integration and continuous deployment pipelines. It executes all test cases and packages the software for deployment. ### 37. Fantastic ecosystem, cross-platform support **Rating:** 4.0/5.0 stars **Reviewed by:** Jonathan Y. | Senior Software Engineer - OpenShift, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** December 17, 2015 **What do you like best about Jenkins?** Jenkins is a very popular CI/CD solution. There are plugins for basically everything, and plugins aren't that difficult to create. It supports Windows, Mac and Linux, which can be important for cross-platform projects as it ensures that all build configurations are consistent and reports are available from a single dashboard. Many projects use it and there is commercial support available from CloudBees and other companies. It's a simplistic architecture, where a Jenkins master controls builds on a number of agents (slaves). No database is needed and upgrades are straightforward (simply requires replacing a WAR file and restarting, and Jenkins has capabilities to allow automated upgrades as well). There are plugins available for managing slave machines (e.g. dynamically provisioning new virtual machines on VMware vCenter or OpenStack). The tooling capability can be used to manage system-level tools (ensuring that NodeJS or Java are available to the build) and to keep them up-to-date. This dramatically improves manageability for build agents, as they are effectively disposable machines (it's quite easy to provision new ones whenever needed from the Jenkins console, as long as your builds don't rely on state that isn't controlled by Jenkins). **What do you dislike about Jenkins?** Jenkins is a bit ugly, though that has improved over time. Service-based solutions like Travis CI and AppVeyor are much better looking, and have better direct integration with GitHub. Additionally, build configurations are kept separate from version control, though there are basic audit logging capabilities. **Recommendations to others considering Jenkins:** Give Jenkins a try! It's exceedingly simple to configure, builds can be set up with just a few clicks, it has a rich plugin ecosystem, and works across platforms. **What problems is Jenkins solving and how is that benefiting you?** Building software projects and running periodic tasks using Java, NodeJS, batch scripts, and other tools. ### 38. Jenkins is highly customisable and good for testing and CI for private repositories. **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Marketing and Advertising | Small-Business (50 or fewer emp.) **Reviewed Date:** December 15, 2015 **What do you like best about Jenkins?** Jenkins can run on your own infrastructure which makes it ideal for testing and deploying private code for work. It has plugins for all my needs it's highly configurable and was easy to integrate with our gitolite hooks. Complex setups can also be re-used by basing new tasks off existing ones. **What do you dislike about Jenkins?** Configuring tasks can require a lot of clicking in the web GUI which creates a slight administrative overhead when making tasks for many small projects, especially when compared to some simpler tools which read their instructions from a configuration file. **Recommendations to others considering Jenkins:** Although it is easy to install Jenkins from your distribution, Jenkins is able update itself and thereby get a version likely much fresher than what is initially distributed. Plugins can also be installed and maintained easily in a similar fashion. There are hosted Jenkins services but it's easy enough to set up on-site that I would recommend it. **What problems is Jenkins solving and how is that benefiting you?** Jenkins runs our tests and checks our code quality when our remote repositories receive new commits. It also checks the code is buildable for production releases. This conveniently alerts us if something is wrong, without us having to actively check anything, so we can focus on work. ### 39. Flexible, well-supported, enterprise-class CI available for free. **Rating:** 5.0/5.0 stars **Reviewed by:** Steve F. | Web Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** December 14, 2015 **What do you like best about Jenkins?** Highly flexible, customizable, and free/open source build automation that actually works well for any automated process. Comes with a wide selection of plugins and a great community. **What do you dislike about Jenkins?** Jenkins is still in need of some visual modernization (full responsive design, updated/customizable icons, minimalistic but effective visual cues, etc.). It would be nice to see an official mobile app as well. **Recommendations to others considering Jenkins:** Try it out. Don't be scared off by a slightly outdated-looking UI - this is a very advanced and modern application. **What problems is Jenkins solving and how is that benefiting you?** In addition to using Jenkins for all of our building and deploying of code (ASP.NET, C#, VB.NET, Classic ASP, static HTML, etc.), we have switched to it for every job that we have. Since it is able to run terminal commands directly (Windows batch commands, PowerShell, Linux bash commands, etc.), we have configured it to run jobs that run SQL commands, sync files, create feeds, load balance our web servers, and more. ### 40. Integrated build system for your projects **Rating:** 4.0/5.0 stars **Reviewed by:** Ananyo S. | Small-Business (50 or fewer emp.) **Reviewed Date:** December 12, 2015 **What do you like best about Jenkins?** Their motto is continuous integration and it really rings true when you see your projects getting built and instantly deployed when you make a simple push. Jenkins is quite easy to set up. It can be configured to pull directly from your repo like github and push to your server at openshift or digitalocean. It shows build status, what process is running and the console output of the process, every build status can be recorded and you can review builds that failed. You can even manually start a build from recent copy. All this can be done from the web interface **What do you dislike about Jenkins?** The web interface in itself is clunky and not so straightforward. I had to jump through some hoops to enable github hooks to build at git push. **Recommendations to others considering Jenkins:** Jenkins is not as easy as github or openshift, both of these have beautiful interface, easy to spot options etc.. It takes some time to configure jenkins if you have never done this before but once it is set up, you can pretty much forget it. Try it once. **What problems is Jenkins solving and how is that benefiting you?** I have a website in openshift that I use to manage the login system of our club. It was hosted on openshift and openshift mandated ssh git access to push but in our network ssh is blocked. Github worked because of https. Used jenkins to sync the repo. Now I could directly push to github and get the job doen, as simple as a push. ### 41. Jenkins Review From A QA Engineer Perspective **Rating:** 4.0/5.0 stars **Reviewed by:** Shayne V. | Test Engineer II, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Jenkins?** Jenkins has worked out very well for continuous integration for our team. It helps keep code cleaner by providing fast feedback if new code pushed into the repository breaks the build. The nightly builds are utilized by QA quite often to perform in sprint testing and write test cases. **What do you dislike about Jenkins?** As a QA Engineer who writes automated tests, I don't personally write code for our application, however, I hear from our developers that updating Jenkins can be quite tedious which is a drawback. For me personally, the UI looks outdated and can be improved upon. **Recommendations to others considering Jenkins:** Giving QA access to your nightly builds greatly improves the QA process and to keep test suites up to date. These builds help QA get an early start with in sprint testing before the official QA process begins. **What problems is Jenkins solving and how is that benefiting you?** Continuous integration helps keep our product cleaner and the nightly builds are great for QA to grab the latest and greatest to perform in sprint testing. QA uses the nightly builds quite often to write up to date test cases before they start official QA. ### 42. An old friend is better two new ones **Rating:** 4.0/5.0 stars **Reviewed by:** Denis B. | Scala Developer and frontend js developer, Marketing and Advertising, Small-Business (50 or fewer emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Jenkins?** * Jenkins very robust and stable software. * Tons of plugins, for almost everything you ever need (that is also limitation) * Very smooth start * Very fast start from build jobs to build pipeline * Pretty simple configuration * Tons of information in internet and working recipes * It is free and open-source **What do you dislike about Jenkins?** Main painful and week point of Jenkins it is it is open-source nature: Tons of plugins - means some of them already pretty old, bugs not fixed. A lot of plugins duplicated own functions and sometimes conflict with other plugins. You need to be prepare yourself to google a peaces information, test them and repeat, while you will not find working recipe for your needs. Old architecture of jobs makes you create tons of jobs that sometimes repeat itself (now jenkins moving to workflow plugin it allows do less copy-paste, but still has some edge cases. e.g it uses groovy 1.8 without possibility to change). Another big disadvantage, it is pretty inconvenient to backup all your configurations. **Recommendations to others considering Jenkins:** Jenkins worth to try, but it will require some time from your build engineer to make it what best suite to you. **What problems is Jenkins solving and how is that benefiting you?** 1. Build, test, deploy front-end code to CDN 2. Build, test, backend code, Github pull requests 3. Make immutable deploys and fast release cycles ### 43. Vital tool in my CI/CD toolbox **Rating:** 5.0/5.0 stars **Reviewed by:** Danny G. | Senior Director, Full-Stack Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** December 10, 2015 **What do you like best about Jenkins?** Jenkins is a comprehensive solution that has covered literally every build scenario I have encountered. When I am not just fooling around and I know I need build solution that is stable, integrates with everything, and scales - I turn to Jenkins. Critical features: * Support for literally anything you want to build * Support for nodes on special targets * Scales * Webhooks, Plugins, Scripting, Integrations * REST API * Remote triggers **What do you dislike about Jenkins?** Bless their hearts, they've really been trying on the UI - and improving, but it still screams legacy and it's fairly clear that their Web UI team hasn't really caught up. It's a turn off for many who look to Travis and others because they're sexier. **Recommendations to others considering Jenkins:** Suffer through the kludgy UI and look to the rich body of blogs and guides to see how others are utilizing Jenkins to solve their problems. While you're builds are probably not exactly alike, it's almost guaranteed that someone has asked the question you're stuck on and posted an answer online. **What problems is Jenkins solving and how is that benefiting you?** Cross-platform builds across many software tools in many languages, complete integration with entire back-office stack (Slack, Intercom, SFDC, Google Apps, GitHub, Jira, Bitbucket, Mandrill, etc), multiple, dependent builds against Pull-Requests and tracked branches, automated versioning and deployment of build artifacts, etc. Jenkins has allowed me to drastically reduce my cost in testing and releasing software, while allowing me to release far more rapidly, with a stronger assurance of acceptance and quality. ### 44. used it extensively for our distributed CI system. also worked on plugin development **Rating:** 5.0/5.0 stars **Reviewed by:** Imran H. | Software Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** December 10, 2015 **What do you like best about Jenkins?** the code readability , and ability to extend mechanism. also deployment is super straightforward. Continuous integration systems are a vital part of any Agile team because they help enforce the ideals of Agile development Jenkins, a continuous build tool, enables teams to focus on their work by automating the build, artifact management, and deployment processes Jenkins’ core functionality and flexibility allow it to fit in a variety of environments and can help streamline the development process for all stakeholders involved **What do you dislike about Jenkins?** hudson documentation itself is not verbose, Poor documentation The most useful information found about Jenkins is on StackOverflow and various strange corners of the internet that careful Googling may sometimes find. The actual documentation for Jenkins is poorly organized and extremely vague and outdated. Documentation for plugins, even the plugins most heavily relied upon, is almost non-existent. Outdated Interface The Jenkins interface seems outdated and clunky by today's standarts.It does not follow good design principles, has no whitespace which makes the views feel crowded and confusing. High overhead Unlike some of the simple and hosted alternatives, users need to host and setup Jenkins by themselves. This results in both a high initial setup time as well as time sunk into maintenance over a projects duration. **Recommendations to others considering Jenkins:** use the latest workflow strucuture as suggested by cloudbees . **What problems is Jenkins solving and how is that benefiting you?** we solve a lot of automation and testing and also artifactory deployment via jenkins. Highly customisable Jenkins is by far the most customizable solution on the market. There are over 400 plugins to support building and testing virtually any project. ### 45. Jenkins Review **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in E-Learning | Mid-Market (51-1000 emp.) **Reviewed Date:** July 25, 2016 **What do you like best about Jenkins?** Below mentioned are the pros of Jenkins: 1) A place.. where dev team can push updated builds and QA can download. 2) build Repository with history maintained 3) Safe, secure and easy to access **What do you dislike about Jenkins?** Place where i have to download published build is quite long. I have to go from no of screens. That irritating. **What problems is Jenkins solving and how is that benefiting you?** Dev team contentiously deploying build with new updates. No need to ask dev team again & again.. is build provided. ### 46. Your new, hardest-working teammate. **Rating:** 4.0/5.0 stars **Reviewed by:** Eric M. | Principal Software Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** December 16, 2015 **What do you like best about Jenkins?** Jenkins is easy to automate and presents a fully self-hosted continuous integration service that is a fantastic alternative to 3rd party (hosted) solutions. It can run just about any task and sit comfortably on a local machine or behind a corporate firewall. **What do you dislike about Jenkins?** As a free (libre) product, the UI in Jenkins leaves a bit to be desired when compared to industry alternatives like Travis. Much of the configuration is bulky, hard to understand, or requires manual intervention via the command line. **Recommendations to others considering Jenkins:** Make sure a sysadmin keeps an eye on the server. Plugin and framework updates are frequent, and once you're hosting your own application, you need to stay ahead of the game with security patches. **What problems is Jenkins solving and how is that benefiting you?** Both continuous integration (automated code testing and deployment) and environment setup. We've been able to shave not just hours but _weeks_ off our development time by automating common tasks with Jenkins! ### 47. Jenkins is a veteran that works well. **Rating:** 3.5/5.0 stars **Reviewed by:** Ján S. | Embedded OS Developer, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** June 24, 2016 **What do you like best about Jenkins?** There's possibility to do anything in Jenkins and it can be easily tried locally. **What do you dislike about Jenkins?** User interface is very ugly. I would expect something neater these days. But it works. **Recommendations to others considering Jenkins:** It takes while to dive in but there's a lot of good documentation. **What problems is Jenkins solving and how is that benefiting you?** Building a custom project with lots of dependencies. ### 48. Jenkins and Mobile **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** April 14, 2016 **What do you like best about Jenkins?** The ease of setup and configuration of new builds. I love the ability to copy builds to create new ones. **What do you dislike about Jenkins?** There needs to be better support for mobile projects and unit testing. Some of this depends on the mobile platform as well and not jenkins. **Recommendations to others considering Jenkins:** I would make sure that Jenkins handles most of what you need without having to download plugins. We found that some of the plugins are hit and miss with the quality. **What problems is Jenkins solving and how is that benefiting you?** We are trying to solve build issues with mobile applications. We are building many different versions and mobile app libraries that require constant integration. Jenkins has helped accomplish a solid build automation environment for our mobile development team. ### 49. Great Product **Rating:** 5.0/5.0 stars **Reviewed by:** Praveen G. | Software Dev Engg, Tech Yahoo, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** April 25, 2016 **What do you like best about Jenkins?** Continuous Integration - This is the most striking feature!! You will be notified immediately incase of build errors or compile time errors for each and every check-in you made into your code base. **What do you dislike about Jenkins?** None. So far. On a minor note, improve the Getting Started with Jenkins documentation and FAQs. Add more material for Automation builds and JUnit Test cases **What problems is Jenkins solving and how is that benefiting you?** Continuous Integration and automated build and runtime configurations and continuous deployment. Time and smooth collaboration are the major take-aways. ### 50. Day job CI **Rating:** 4.5/5.0 stars **Reviewed by:** Pavel S. | Lead Python Developer, Small-Business (50 or fewer emp.) **Reviewed Date:** February 07, 2016 **What do you like best about Jenkins?** 1. The huge amount of plugins and frequent release rate. 2. Relatively easy set up and maintainance; the strong community helps by adding docs for common scenarios (e.g how to setup proper https rewrites with nginx). **What do you dislike about Jenkins?** The UI can be slow at times; when switching between sections, and in general the UI feels outdated (compared to other CI tools such as Travis). Also, the documentationof of built-in features (especially security) could be improved. **Recommendations to others considering Jenkins:** All you need is a machine with Java, and you have a CI platform in-house. I suggest googling for CI tutorials, but it's relatively easy to set up. **What problems is Jenkins solving and how is that benefiting you?** Automated testing and deployment to certain environments; rarely need to do that manually anymore. ## Jenkins Discussions - [What is Jenkins used for?](https://www.g2.com/discussions/what-is-jenkins-used-for) - 2 comments, 1 upvote - [Is there any plan to change jenkins UX/UI](https://www.g2.com/discussions/is-there-any-plan-to-change-jenkins-ux-ui) - 1 comment, 1 upvote - [Does it integrate with Microsoft Project?](https://www.g2.com/discussions/13687-does-it-integrate-with-microsoft-project) - 1 comment, 1 upvote - [View Jenkins pricing details and edition comparison](https://www.g2.com/products/jenkins/reviews?page=10§ion=pricing&secure%5Bexpires_at%5D=2026-08-08+12%3A25%3A01+-0500&secure%5Bsession_id%5D=87f99cf0-41eb-472b-9fd5-c8f7c310dc77&secure%5Btoken%5D=a73457d8f57df68efda513b795250b48e02ea518ced53f36f188159afacf2f34&format=llm_user) ## Jenkins Integrations - [Amazon EC2](https://www.g2.com/products/amazon-ec2/reviews) - [Amazon EC2 Auto Scaling](https://www.g2.com/products/amazon-ec2-auto-scaling/reviews) - [Amazon Elastic Container Registry (ECR)](https://www.g2.com/products/amazon-elastic-container-registry-ecr/reviews) - [Amazon Elastic Kubernetes Service (Amazon EKS)](https://www.g2.com/products/amazon-elastic-kubernetes-service-amazon-eks/reviews) - [Amazon S3 Glacier](https://www.g2.com/products/amazon-s3-glacier/reviews) - [Apache Maven](https://www.g2.com/products/apache-maven/reviews) - [AWS Cloud Development Kit (AWS CDK)](https://www.g2.com/products/aws-cloud-development-kit-aws-cdk/reviews) - [AWS CodePipeline for CI/CD Automation](https://www.g2.com/products/aws-codepipeline-for-ci-cd-automation/reviews) - [Azure DevOps Server](https://www.g2.com/products/azure-devops-server/reviews) - [Azure Portal](https://www.g2.com/products/azure-portal/reviews) - [Bitbucket](https://www.g2.com/products/bitbucket/reviews) - [BlueOceanAI (Formally BlueOcean Brand Navigator)](https://www.g2.com/products/blueoceanai-formally-blueocean-brand-navigator/reviews) - [BrowserStack](https://www.g2.com/products/browserstack/reviews) - [Codex](https://www.g2.com/products/openai-codex/reviews) - [Discord](https://www.g2.com/products/textaify-discord/reviews) - [Docker](https://www.g2.com/products/docker-inc-docker/reviews) - [Git](https://www.g2.com/products/git/reviews) - [GitHub](https://www.g2.com/products/github/reviews) - [GitLab](https://www.g2.com/products/gitlab/reviews) - [Gradle Build Tool](https://www.g2.com/products/gradle-build-tool/reviews) - [Grafana Labs](https://www.g2.com/products/grafana-labs/reviews) - [IBM Vault (formerly HashiCorp Vault)](https://www.g2.com/products/ibm-vault-formerly-hashicorp-vault/reviews) - [Jira](https://www.g2.com/products/jira/reviews) - [Jira Service Management](https://www.g2.com/products/jira-service-management/reviews) - [JUnit](https://www.g2.com/products/junit/reviews) - [Kubernetes](https://www.g2.com/products/kubernetes/reviews) - [Microsoft Teams](https://www.g2.com/products/microsoft-teams/reviews) - [npm](https://www.g2.com/products/npm/reviews) - [Selenium Grid on Windows](https://www.g2.com/products/selenium-grid-on-windows/reviews) - [ServiceNow IT Service Management](https://www.g2.com/products/servicenow-it-service-management/reviews) - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews) - [SonarQube](https://www.g2.com/products/sonarqube/reviews) - [Worksoft Certify](https://www.g2.com/products/worksoft-certify/reviews) ## Jenkins Features **Functionality** - Deployment-Ready Staging - Integration - Extensible **Management** - Configuration Management - Access Control - Orchestration - Portfolio Management - Workflow Management - Timeline Management - Testing Management - Change Management - Issue Management - Compliance Management - Policy Management - User Management - Application Management - Task Management - Project Management - Release Management - Audit Management **Functionality** - Third-Party Integrations - Extensibility - Test Customization **Agentic AI - AWS Marketplace** - Autonomous Task Execution - Multi-step Planning - Cross-system Integration **Management** - Processes and Workflow - Reporting - Automation **Functionality** - Automation - Integrations - Extensibility - Continuous Integration - Third-Party Integrations **Management** - Automation - Processes and Workflow - Reporting **Processes** - Pipeline Control - Workflow Visualization - Continuous Deployment - Prioritization - Version Control - Rules-Based Workflow - Approval Workflow - Configurable Workflow **Agentic AI - Continuous Integration** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance **Agentic AI - Continuous Delivery** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance **Additional Functionality** - Single Sign On - Search/Filter - Real-Time Reporting - Data Import/Export - Reporting/Analytics - AI Copilot - Commenting/Notes - Data Extraction - SSL Security - Performance Metrics - Status Tracking - Real-Time Monitoring - Troubleshooting Reports - API - Issue Tracking - Projections - Real-Time Data - Event Logs - Collaboration Tools - Generative AI - Role-Based Permissions - Monitoring - Activity Dashboard - Authentication - KPI Monitoring - Activity Tracking - Real-Time Notifications - Dashboard **Additional Functionality** - Continuous Deployment - Source-Code Scanning - Continuous Delivery - Prioritization - Generative AI - Compliance Management - Data Import/Export - Access Controls/Permissions - Bug Tracking - Reporting/Analytics - For Developers - Issue Management - Repository Management - Workflow Management - Monitoring - Pipeline Management - Application Management - API - AI Copilot - Configuration Management - Data Storage Management - Multi-User Collaboration - Project Management - Version Control - Activity Dashboard - Data Synchronization - Lifecycle Management - Change Management - Status Tracking - Authentication - Alerts/Notifications - Automated Testing - Debugging - Approval Process Control - Build Log - Quality Assurance ## Top Jenkins Alternatives - [GitHub](https://www.g2.com/products/github/reviews) - 4.7/5.0 (2,332 reviews) - [CloudBees](https://www.g2.com/products/cloudbees/reviews) - 4.4/5.0 (591 reviews) - [CircleCI](https://www.g2.com/products/circleci/reviews) - 4.4/5.0 (501 reviews)