G2 Crowd gives a real-time look at how dreamforce sponsors and exhibitioners stack up.

Jenkins

4.3
(204)

Jenkins is an application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

Work for Jenkins?

Learning about Jenkins?

We can help you find the solution that fits you best.

Jenkins Reviews

Ask Jenkins a Question
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • For Category
  • Industry
Ratings
Company Size
User Role
For Category
Industry
Showing 206 Jenkins reviews
LinkedIn Connections
Jenkins review by Himani S.
Himani S.
Validated Reviewer
Verified Current User
Review Source

"Jenkins - Review"

What do you like best?

Jenkins is one of the best Continous development tools in the market. It can automatically run test jobs whenever you push your code to a repository. Hence easily, issues can be identified and even the code can run for dependency errors on a remote machine. provides accurate build logs for a particular job with regular success/failure email notifications to concerned users. Jenkins can integrate with almost any external system used for developing applications which means that you worry less about your tooling and more about delivering good code.

What do you dislike?

I haven't come across anything which I don't like about jenkins. However, UI can be improved a bit.

What business problems are you solving with the product? What benefits have you realized?

I use Jenkins to provide continuous integration of application code and often use it for continuous deployment as well. Jenkins can watch source code repositories for changes and immediately pull that code and send it through a battery of steps designed to ensure that no problems were introduced into the code when it is integrated with other developer's code.

Sign in to G2 Crowd to see what your connections have to say about Jenkins
Jenkins review by Dylan C.
Dylan C.
Validated Reviewer
Verified Current User
Review Source

"The best CD tool out there "

What do you like best?

How incredibly useful Jenkins can be. No better tool exists for integrating your repositories and code bases with your deployment infrastructure. It can automatically run test jobs and create artifacts whenever you push your code to a repository. If those checks fail, it will notify you to come and fix the issue. On top of this, there are a ton of plugins and other customizable settings that allow you to make jenkins jobs for almost any application or deployment- small or large.

What do you dislike?

The UI is a little ugly. While the application is still incredibly useful, the GUI could use some touching up here and there to make it more appealing to look at and navigate. A lot of the progress features and icons are super pixellated and don't refresh automatically when jobs finish. This is a very small, somewhat insignificant issue and does show how great jenkins is as a tool. It is also a free application so it is understandable that they wouldn't be able to apply the same polish as a licensed app.

Recommendations to others considering the product

learn it well and it will become your most valuable tool.

What business problems are you solving with the product? What benefits have you realized?

Solving our deployment issues. Since we are employing a devops infrastructure, we have committed to consistently deploying our applications weekly if not more. This means we don't have the time to sit down and manually deploy our code and check that it passes our tests each time it is updated. By automating that entire process with jenkins, a 3-man team can now support 5+ apps compared to before where they would be supporting only 1-2.

What Continuous Integration solution do you use?

Thanks for letting us know!
Jenkins review by Gurleen S.
Gurleen S.
Validated Reviewer
Verified Current User
Review Source

"Jenkins - Continuously Providing Integrated Solutions"

What do you like best?

Jenkins provides easy to use interface when it comes to configuring almost anything with respect to Jobs, Admin configurations, Plugins. Although, Jenkins provide many out of the box functionality, it also has wide variety of plugins to support continuous integration best practices. Jenkins can be integrated with different source control management tools, build automation tools, code quality tools. Jenkins can generate the test reports in xml format which can be emailed to developers on every job execution. Jenkins also provides file fingerprinting option which is helpful when there are multiple dependencies among different projects in Jenkins. Jenkins provides accurate build logs for a particular job with regular success/failure email notifications to concerned users.

What do you dislike?

I have not come across anything which I dislike about Jenkins.

Recommendations to others considering the product

I would recommend Jenkins as the most easily configurable and easily managed tool for on-boarding applications for continuous integration and continuous delivery. Moreover, it has got features which are helpful even for a naive user to get started and perform activities such as integrating the source code management tool, build automation tool, code quality tool, deployment scripts, servers to which the applications are to be deployed to and other available options and plugins.

What business problems are you solving with the product? What benefits have you realized?

I have integrated different DevOps tools with Jenkins and formed many end to end release pipelines. After using Jenkins, the build and deployment time has significantly reduced which in turn has reduced the effort for performing manual releases every time.

Jenkins review by Christopher M.
Christopher M.
Validated Reviewer
Verified Current User
Review Source

"Great community support, many additionally plugins, very easy to learn and use"

What do you like best?

The two things I like most about Jenkins: the tremendous community adoption, and the rich environment of plugins available to download. Jenkins has been around for a while and for the most part you are not going to run into an issue that hasnt already been asked/resolved on SO or another forum. Additionally, Jenkins has a great plugin platform for extensibility and additional functionality

What do you dislike?

The worst thing about Jenkins (and this isn't exclusive to Jenkins), is that the support for containerization just isnt there yet. Not to say it doesn't exist, but it's not very mature and it's almost like putting a square peg in a round hole. In many environments Jenkins is becoming moot because of this.

Recommendations to others considering the product

Think about how you want to set up your builds before you jump right in. We created a pretty cruddy pipeline in the beginning and as a result our deployments took 15x as long as they should have. Also, if you are thinking of building a plugin, it would be nice to have vendor specific plugins that address specific issues related to those platforms (such as liferay, hybris, etc).

What business problems are you solving with the product? What benefits have you realized?

We are solving automated deployments and I guess a bit of automated building as well. Additionally we use jenkins for regression testing and it's an essential part of our CI operations

Jenkins review by Samuel B.
Samuel B.
Validated Reviewer
Verified Current User
Review Source

"The Standard for On-Premise CI Servers"

What do you like best?

Jenkins is the standard in continuous integration servers that are deployed on premise because it was one of the first products available in this space and it has continued to innovate. Jenkins can integrate with almost any external system used for developing applications which means that you worry less about your tooling and more about delivering good code. More recent tools that are cloud-based like CircleCI, TravisCI and CodeShip provide similar features but do not have the comprehensive plugin integration that Jenkins still has. Anyone using Jenkins also benefits from years of other developers using the product and solving problems meaning that it is rare that you will run into an issue with this tool that hasn't already been solved.

What do you dislike?

Jenkins is still heavily plug-in based to add functionality to the base system. Upgrading and maintaining plugins to get desired functionality can sometimes be frustrating and time consuming. Upgrading some plugins can sometimes break the functionality of other plugins leading to breaking jobs that were previously working. This is less prevalent than it used to be but anyone managing a Jenkins instance must be cautious about upgrading plugins and breaking user jobs. That being said, you will not find a greater breadth of plugin variety in any other tool on the market. Jenkins can connect to almost anything which makes integrating with your system of choice a much easier task.

Recommendations to others considering the product

If you require an on-premise (inside the firewall) CI system then Jenkins will be easy to setup and start using in a very short period of time. You can always find help online solving any Jenkins issues you come across so you feel supported and that you won't have to spend time troubleshooting your CI install. If you are open to using cloud tools and you have a simple build then it is worth considering other options because Jenkins is not offered as a cloud service.

What business problems are you solving with the product? What benefits have you realized?

I use Jenkins to provide continuous integration of application code and often use it for continuous deployment as well. Jenkins can watch source code repositories for changes and immediately pull that code and send it through a battery of steps designed to ensure that no problems were introduced into the code when it is integrated with other developer's code. Jenkins can execute any step you can program but common steps include unit testing, integration testing, source code analysis, dependency vulnerability scanning and end-to-end testing.

Jenkins review by DaShaun C.
DaShaun C.
Validated Reviewer
Verified Current User
Review Source

"Dependable and affordable automation"

What do you like best?

The community behind Jenkins is amazing. I've used and managed Jenkins (and Hudson) exhaustively for years and have never been the first come up with a great tool idea or workflow.

What do you dislike?

I think the UI is still lacking. I like to use my mobile device when needed. The "Blue Ocean" is a step in the right direction but doesn't seem ready for prime-time yet.

Recommendations to others considering the product

Jenkins should be the first step of any development project. It's affordable and easy to setup. There is a 90% chance that your workflow has already been used in production by someone in the community, and they have documented it with easy to follow examples. Use the "jenkinsfile" approach if you can!

What business problems are you solving with the product? What benefits have you realized?

It is part of our continuous automated testing and deployment workflow. We have hooks in place to move artifacts through multiple gates and multiple environments. We also use it for automated integration testing of multiple environments, triggered periodically, in addition to the build/deployment pipelines.

Jenkins review by Hazzim A.
Hazzim A.
Validated Reviewer
Review Source

"Jenkins for CI/CD."

What do you like best?

We are working with jenkins in all environment (Dev, QA, Stage and production) and the integration of Jenkins and third party plugins (Git, Mesos, Maven, artifactory) works great for all the workflow from Dev to prod, RBAC for access control works great with AD integration and the setup of new jobs/pipelines is very easy.

What do you dislike?

with some upgrades the third party plugins just broke and we need to do some workarounds until the plugin got updates, so, keep in mind you need testing deeply before upgrades and try to always use a LTS version.

Recommendations to others considering the product

Jenkins will be your best option thanks to all plugins available, but be very careful with upgrades or your third party plugins could fail, try to work with LTS version and install just the minimal plugins you could need.

What business problems are you solving with the product? What benefits have you realized?

Control and integration of all the workflow with one tool, that include plugins to work with new technologies that are working with (GIT, Maven, Java, Python, Docker, Mesos, Oracle Cloud, Hadoop, SPARK)

Jenkins review by Tiffany L.
Tiffany L.
Validated Reviewer
Verified Current User
Review Source

"Great, free continuous integration tool"

What do you like best?

I love that the product is free and has so much customization via user created plugins.

What do you dislike?

The slave node default workspace cannot be configured per slave node.

Recommendations to others considering the product

Look at the available plugins to see how many different use cases you can achieve.

What business problems are you solving with the product? What benefits have you realized?

It provides cost savings and can provide multiple uses. Jenkins allows us to sync up with Jira and Bitbucket so we can have builds triggered automatically. We have the ability to speed up building by having parts of the build run concurrently. We even use it to run some metrics tools and run unit tests to generate reports. It allows us to integrate changes among different teams by providing builds faster by having the pre-configured.

Jenkins review by Ritwik K.
Ritwik K.
Validated Reviewer
Verified Current User
Review Source

"Best software for Build Automations"

What do you like best?

This has the tremendous advantage of always knowing if all tests work and getting fast feedback. The fast feedback is important so you always know right after you broke the build (introduced changes that made either the compile/build cycle or the tests fail) what you did that failed and how to revert it.

What do you dislike?

Kind of complex though! Like, it takes time to know whats the reason for error and work on it.

Eventhough you get to know the error, it works one day but no the other day. Issues like, network issues,space issues, and even, the server of the tool you use might be over consuming.. and many other reasons which are not in our hands.

What business problems are you solving with the product? What benefits have you realized?

Jenkins enables us to do Faster QA and deployment cycles.

We have integrated Jenking with Regression to reduce QA efforts.

Jenkins review by Anuradha W.
Anuradha W.
Validated Reviewer
Verified Current User
Review Source

"Easy to use, setup and configure"

What do you like best?

With Jenkins Versions 2 and later, it has become really easy for us to setup and use Jenkins. There are plenty of plugins available which helps us automate most of the jobs we have as well. UI is simple and easy to learn.

Jenkins is used to automate our daily build processes.

What do you dislike?

Even though the UI is simple, we'd like a little more graphics. Some plugins are not compatible with the latest version, and most plugins get abandoned after a while.

Recommendations to others considering the product

I would highly recommend Jenkins to anyone trying to automate certain manual processes. It has helped us solve a lot of issues we have had with our current manual build processes. Also it's visual representation of the status and current progress of builds help us in monitoring and troubleshooting tasks.

It is also easy to setup and configure, and lets you get started within less than an hour. Some external plugins available are not compatible with the latest version and some are no longer supported, so I'd advise anyone using to be careful when using plugins, make sure you use plugins that will be supported on long term.

We're excited to see what Jenkins blue ocean UI plugin has to offer us. For now it is still in beta version, and hopefully it will replace the current UI with a more modern look and feel.

What business problems are you solving with the product? What benefits have you realized?

We have a build process that uses CMD files and they're triggered within cmds itself, but with Jenkins, we can easily schedule these scripts as well as get a visual representation of the status and the progress of the build.

Jenkins review by Yoanis G.
Yoanis G.
Validated Reviewer
Review Source

"Most flexible CI/CD system ever"

What do you like best?

The very best thing I like about Jenkins is it's flexibility. I mean, you can do anything with Jenkins (as long as there is a plugin). There is a learning curve of course but after you've mastered it the sky is the limit. Another thing I like about Jenkins is how easy it is to setup. With Jenkins 2.0 you're good to go in about 5 mins.

What do you dislike?

What is dislike about Jenkins is, it's user interface. You can clearly tell that there is a lack of love there (even after the work that was done with Jenkins 2.0). Another thing that needs improvement is more native support for containers and also for Pipeline as Code.

Recommendations to others considering the product

Getting productive while using Jenkins might take some time. Be patient. You will get there. Also keep in mind that despite the issues you will be able to do pretty much anything you want.

What business problems are you solving with the product? What benefits have you realized?

I've used Jenkins mainly for doing Continuous Integration and Build Automation.

Jenkins review by Administrator in Financial Services
Administrator in Financial Services
Validated Reviewer
Verified Current User
Review Source

"After you learn about benefits, you create a new world of automation"

What do you like best?

Secure;

Lots of Automation. You may automate deploy, build, and everything you need. All with dashboards, centralized interface, and split by logical folders. All integrated in active directory or other authentication;

A variety of plugins to choose, as input and output;

Alerts;

In resume, you may automate the build of your software, and deliver in development, QA and production environments, all monitored and with logging/audit of who is running what job, and when was executed.

What do you dislike?

The time you need to learn to use, if you're trying to use it alone. If you learn from someone that already use it, it's really fast to learn.

Recommendations to others considering the product

If you already use a tool like this, maybe this tool is not for you. But, if you don't have any tool to automate stuff, give it a try, because you only need a server to start, as the software is opensource. It will already help you with lots of stuff. From simple Windows scripts, to more complex, like build and deploy to Kubernetes, in different environments, with aproval of different users, alerting in a slack or another tool, all this Jenkins will help you to solve. It may be manually started, event driven, or another way you choose to use it. The setup, as it is a orchestrator, is fast and requires to know the other servers more than Jenkins server, like credentials, paths, executables, source and destination and what you need to execute there. Have fun with Jenkins!

What business problems are you solving with the product? What benefits have you realized?

Automation;

Audit;

Safety;

Jenkins review by User
User
Validated Reviewer
Verified Current User
Review Source

"Best Continious Integration Tool"

What do you like best?

Simple and Quick Installation / Setup and Configuration. Light weight. Can be deployed on a simple light weight server like Tomcat. Small memory foot print. Able to run in a Master Slave configuration executing the Jobs in the Slave Nodes orchestrated by the Master. Tons of plugins available to integrate with the other tools and products. Best in class product.

What do you dislike?

Creating multiple jobs is laborious and time consuming. Duplication of the configuration in the jobs results in a major rework if anything has to be changed across the board. Difficulty in running huge build with 1000s of test cases and Hundreds of thousand lines of code which can generate tons of logs during the build which may result in a Jenkins server crash.

Recommendations to others considering the product

Very good tool for implementing the CI / CD Pipeline in an organization

What business problems are you solving with the product? What benefits have you realized?

Was able to do a seamless Continuous integration of the Code

Jenkins review by Pascal L.
Pascal L.
Validated Reviewer
Verified Current User
Review Source

"Highly customizable automation tool"

What do you like best?

The software is highly open source and has a rich community that generate plugins.

Since version 2.x pipeline has code is truly a game changer.

What do you dislike?

Since the community is generating a lot of plugin, quality of these plugins is variable.

There is a lot of missing native support for trivial items that requires plugins to be able to work

Recommendations to others considering the product

There is a lot of automation tool and solution, Jenkins is a great and free.

What business problems are you solving with the product? What benefits have you realized?

Jenkins let us automating a lot of the software build pipeline. And provide a great platform to expose the results.

Jenkins review by Sarah P.
Sarah P.
Validated Reviewer
Review Source

"Easy enough to use you'll wonder why the won't let you"

What do you like best?

As a Front End Developer, I love that Jenkins makes it easy to deploy changes, you can see which environments you are using. I also loved that you customize what files are being deployed etc.

What do you dislike?

The setup can be complicated. Sometimes it would take refreshing to show that it was done deploying

Recommendations to others considering the product

It's a great open source tool, that is fairly easy to set up. It would be worth it to offload some of the efforts of maintenance or setup though, as after a while it eats into the easiness of it.

What business problems are you solving with the product? What benefits have you realized?

Continuous integration issues, it's very frustrating to just need to have a small fix, but be unable to navigate it's deployment to production individually. Especially when dealing with smaller projects.

Jenkins review by Administrator in Telecommunications
Administrator in Telecommunications
Validated Reviewer
Verified Current User
Review Source

"CloudBees Jenkins Enterprise."

What do you like best?

How widely adopted it is in the industry which means lots of supported technologies is one of the biggest things to me. The ease of use and the pipeline features are invaluable to us.

What do you dislike?

The interface could be better. Browsing from the top-level down can be a little cumbersome - especially in the Enterprise version spread across many master servers. Also, some of the context menus and switching could be improved. As far as overall functionality however, there isn't much I dislike.

Recommendations to others considering the product

Start small. Utilize VMs as much as possible for the server and slaves both. Make sure you utilize pipeline groovy scripts from the beginning and avoid using unapproved CloudBees plugins even if you are still using the open source version. Also, using Jenkinsfiles along with the github integration makes things so much easier when adopting.

What business problems are you solving with the product? What benefits have you realized?

We are using it for our software builds. We use it for continuous integration and delivery of hundreds of software systems with hundreds, if not approaching 1000s, of software components worldwide.

Jenkins review by Gautam A.
Gautam A.
Validated Reviewer
Review Source

"Awsome CI and CD tool"

What do you like best?

Jenkins is an awesome Continuous integration and Continuous deployment tool, You can deploy your code on any cloud system from any source code repositories.Its biggest advantage is its plugin architecture. You can install plugins as per your need. you can use its scaling mode to run multiple deployment at the same time.

What do you dislike?

Administrating Jenkins can be a hectic task for newbie. Its documentation is good but still it is hard to figure out which feature and function to enable and which to disable. Sometime plugin functions can conflict with each other.

Recommendations to others considering the product

Instead of manually deploying code, use jenkins to automate your task and save resources and efforts.

What business problems are you solving with the product? What benefits have you realized?

We are using jenkins to deploy code on our development and production servers.

Jenkins review by Grant W.
Grant W.
Validated Reviewer
Verified Current User
Review Source

"Jenkins review"

What do you like best?

I like the way that jenkins integrates with a lot of external systems. we also like It is a server-based system running in a servlet container like the Apache Tomcat.

It offers support for SCM platforms and solutions like AccuRev, CVS, Subversion, Git, Mercurial, Perforce, Clearcase and RTC, and can implement Apache Ant and Apache Maven-based projects. Jenkins can also execute arbitrary shell scripts and Windows batch commands.

What do you dislike?

I do not like how it is configurable, seems to be about 20 years out of date.

Recommendations to others considering the product

I would recommend Jenkins to anyone who is looking for a continuous integration tool that delivers continuous integration services for software development.

What business problems are you solving with the product? What benefits have you realized?

We use jenkins as a continuous integration tool that delivers continuous integration services for software development.

Jenkins review by John K.
John K.
Validated Reviewer
Verified Current User
Review Source

"Ok but the UI is pretty bad and the scheduling facility is awful."

What do you like best?

First off, I need to qualify my review by saying that I don't have much experience with other build tools and I'm a fairly novice Jenkins users. Jenkins has ALOT of in-built functionality, almost to a fault (see dislikes).

What do you dislike?

First off, we're on version 1.6 and the UI leaves alot to be desired. Also, the tool is not particularly user friendly and, as other reviewers have mentioned, some functions (like job configuration) are overly complicated and cumbersome. One of my biggest gripes is the lousy, antiquated job scheduling using CRON. Really? That's technology from the 1970s. In fact, the scheduling is so bad that I end up using the options to kick-off builds from the command line and then use Windows Task Manager. I guess the old adage applies: you get what you pay for and this open source tool is no exception.

Recommendations to others considering the product

Maybe some of the UI drawbacks have been fixed in the latest version. At the very least, make sure you try out the scheduling facility if that is important to you and make sure to look at the job configuration page.

What business problems are you solving with the product? What benefits have you realized?

We needed a tool to facilitate Continuous Integration. I wasn't involved in the tool selection process and somehow we ended-up with Jenkins. Personally, I would have kept looking for a tool with a richer, more user-friendly interface and a real scheduling facility.

Jenkins review by Jerry W.
Jerry W.
Validated Reviewer
Verified Current User
Review Source

"Perfect UI for Automation Frameworks"

What do you like best?

We all know this project for it's superb CI/CD abilities and malleable scripting interfaces. I am sure many have found many other uses for Jenkins. Personally I have found it to be an incredibly quick to market, secure and performant user interface for launching automated tests. With fantastic plugins that provide instant traceability, login management and statistics, Jenkins provides a robust platform for wiring up the latest test frameworks.

What do you dislike?

There's not much to dislike about Jenkins. The open source community is very supportive. That can make upgrading and patching a little hectic. The look and feel is aging a bit. Race conditions are also difficult to manage from one OS to another.

Recommendations to others considering the product

There are some great CI/CD products out there but if you're looking to get up and running quickly with the latest standards and great community support, why would you not use Jenkins?

What business problems are you solving with the product? What benefits have you realized?

Automation Framework UI and Internal Tools Launchpad. The benefits have been ease of use, good traceability, and instant credibility with the developer community.

Jenkins review by Teresa K.
Teresa K.
Validated Reviewer
Verified Current User
Review Source

"Easy enough to get going without running into too many problems, not flexible enough for all situati"

What do you like best?

It is very easy to get it installed and start testing various build options. I like being able to use slave instances...gives you the opportunity to build a robust build farm. I like how easy it is to send build information to interested parties.

What do you dislike?

Even though there are hundreds of plug-ins, it still surprises me how often I have to write something that will fit a unique situation. It uses up a ton of memory, and after a few CI runs, more and more. Some Jenkins releases are better than others, so if one is not too bad, I'm very reluctant to upgrade to a new one. I don't like that I can't narrow down CI builds to each individual change. That's a pain.

Recommendations to others considering the product

It is worth the cost. : ) Truly, though, it is worth the cost of the time to set up and test to see if it meets your needs.

What business problems are you solving with the product? What benefits have you realized?

Needed to get builds running fast. Installing on Windows is very easy; installing on Linux is pretty easy. It's easy to hook up with existing CI tools by using slave instances. It's great to do build automation because it lets me create builds in my sleep. Continuous integration saves a lot of time and resources because it lets us know if there is a problem with the build right away, rather than having to wait for the automated (nightly) build or, egad, when QA gets it.

Jenkins review by RISHANT A.
RISHANT A.
Validated Reviewer
Verified Current User
Review Source

"Jenkins - An open Source awesome tool"

What do you like best?

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?

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 the product

GO for it !! Its amazing .

What business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Tonya E.
Tonya E.
Validated Reviewer
Verified Current User
Review Source

"Good CI tool, lots of plugins for enhancement"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Peter R. G.
Peter R. G.
Validated Reviewer
Verified Current User
Review Source

"We use Jenkins heavily, for builds, deployments, and datacenter management."

What do you like best?

I like that it is open, free, and has many plugins, which are also free.

What do you dislike?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Administrator in Sports
Administrator in Sports
Validated Reviewer
Verified Current User
Review Source

"Control Automation Testing via Jenkins"

What do you like best?

We use Jenkins to run our automated test suites via the click of a button. The user gets to choose:

-What tags to run

-How many VM's to run against, via the available pool

-What stag/prod env to run against

-What GitHub branch to run against

This alleviates users having to do things via the command line, and for non-technical users that can sometimes be cumbersome.

Along with the Jenkins plug-in for Cucumber Reports, it produces a nice pretty HTML report of the test run where you can look at passing/failing tests and drill down into any single test to analyze the log, etc. You can also add the Slack plug-in to get the HTML report sent out via slack (or email, etc.).

What do you dislike?

Jenkins, for the most part, is easy to configure, but some of the help pages for Jenkins do not give the best examples on how to set things up from scratch. Novice users may encounter a few challenges on setup.

Recommendations to others considering the product

Open source software, good stuff!

What business problems are you solving with the product? What benefits have you realized?

Running automated test suites via the click of a button.

Jenkins review by Mitchell B.
Mitchell B.
Validated Reviewer
Verified Current User
Review Source

"Works exactly as expected"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Paweł G.
Paweł G.
Validated Reviewer
Verified Current User
Review Source

"Automating Android builds with Jenkins"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Babur D.
Babur D.
Validated Reviewer
Verified Current User
Review Source

"Free, mature and easy to configure"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Tyler B.
Tyler B.
Validated Reviewer
Verified Current User
Review Source

"Excellent product - easy to learn & configure!"

What do you like best?

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?

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 the product

Would definitely recommend to any large team that needs continuous integration.

What business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Csaba K.
Csaba K.
Validated Reviewer
Verified Current User
Review Source

"Review of Jenkins CI"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Mark A P.
Mark A P.
Validated Reviewer
Verified Current User
Review Source

"Jenkins has many false starts issues."

What do you like best?

Supports Java builds with maven and ant, bash shell scripting, remote login where Java agents execute.

What do you dislike?

Initiates false starts so you have write rules to handle these use cases.

Heavy GUI Java implementation.

No thin client support.

Plug-ins don't always work with core version your using. May required to upgrade core, which corrupts your own written plug-ins installed.

Linux LDAP/NIS support is lacking.

Build restarting on false starts is not possible, without additional scripting. Plug-ins are weak in this functionality.

Recommendations to others considering the product

Jenkins is best used in single threaded CI

What business problems are you solving with the product? What benefits have you realized?

Replacement for Build Forge due to management thinks free is less costly after you have already purchased the licenses and then dropped all support.

Jenkins review by Michelangelo v.
Michelangelo v.
Validated Reviewer
Verified Current User
Review Source

"Jenkins, the easiest way to start with automation workflows and continuous integration"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Ipshita A.
Ipshita A.
Validated Reviewer
Review Source

"CICD Master"

What do you like best?

The best part about Jenkins is the ease of locating my working repositories with respect to my bitbucket. Also, it puts down a number of build types that I would want to perform on my project.

Apart from that the detailed report or "console output log" that Jenkins provides after each job is really impressive. In case of failures, it provides any input that may help to resolve the fail.

What do you dislike?

The huge amount of plugins that I have to import before building is pretty tiring.

Recommendations to others considering the product

Jenkins is a perfect platform for all your CICD problems.

What business problems are you solving with the product? What benefits have you realized?

We are using Jenkins for all our builds and quality check and of course CICD.

Jenkins review by Ashokekumar S .
Ashokekumar S .
Validated Reviewer
Review Source

"Capability to drive Enterprise CI with diversified tech stack"

What do you like best?

Simplicity & ease of use. Great extension capabilities

What do you dislike?

Inbuilt reporting capability can be improved a lot

Recommendations to others considering the product

Jenkins a powerful tool with a lot of capabilities, we need to have a good knowledge on the system to effectively use it. Choice of right plugins and right CI architecture is key to success. In the past 3 years we have hardly come across any limitations in using the product. For most of your questions the answers are already available in the forum, this will ensure we don't reinvent the wheel often

What business problems are you solving with the product? What benefits have you realized?

Supporting divers technology base with the same ease. Usefull plugins and ability to seamlessly integrate with any system in the engineer life-cycle. A robust product to support large users and volume of CI activities, with a very small central support team

Jenkins review by Gaël R.
Gaël R.
Validated Reviewer
Verified Current User
Review Source

"A Good Old Continuous Integration Software"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Junxiao S.
Junxiao S.
Validated Reviewer
Verified Current User
Review Source

"Useful but often breaks down"

What do you like best?

triggers a build whenever code is pushed to Gerrit code review

What do you dislike?

slave nodes often breaks down, and require manual intervention to repair

Recommendations to others considering the product

You need to spend time setting up and repairing slave nodes to run builds. Jenkins itself is free, but your time is not.

What business problems are you solving with the product? What benefits have you realized?

Jenkins can verify the quality of code commits, and ensure the code builds on every supported platform; we don’t have to equip many VMs for each developer

Jenkins review by Attila C.
Attila C.
Validated Reviewer
Verified Current User
Review Source

"Jenkins the great CI tool"

What do you like best?

Wide range of language support

Flexible continuous build pipelines

Easy to define jobs with elastic hooks

Can integrated with several SCM systems

What do you dislike?

The user interface design can be improved with responsive design and material sytle

Recommendations to others considering the product

Jenkins is easy to use with great support and easily can be configured via the simple UI interface.

You can utilise for both back-end and front-end projects effectively.

What business problems are you solving with the product? What benefits have you realized?

Continuous deployment flows with nightly builds, instant build status feedback

Auto deploy into QA environments easily, testing features before production state

Auto build after each commit thanks to git hooks, so development team rapidly see test results and code quality reports

Auto deployment to docker AWS instances

Jenkins review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Verified Current User
Review Source

"DevOps Engineer at Refinery29"

What do you like best?

Jenkins is tested, well-known system with a decent ecosystem of plugins and support.

What do you dislike?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

I've always used Jenkins whenever we need an interface to keep track of, and run, jobs.

Jenkins review by Tushar B.
Tushar B.
Validated Reviewer
Review Source

"Excellent tool for continuous integration"

What do you like best?

Everything works so seamlessly. The documentation is pretty good and straightforward. It works in combination of many external systems such as Jira, Git, etc. which is awesome because most companies use these and using Jenkins goes without saying.

What do you dislike?

The only part I dislike is the UI. It definitely needs to be improved. Job importing and other plugins sometimes don't work.

Recommendations to others considering the product

If you use Git, Jira, and many such tools, Jenkins goes well with these so please try it out. It is one of the very good out of the box tools that will make your life easier.

What business problems are you solving with the product? What benefits have you realized?

Code building and deployments.

Jenkins review by Ethan C.
Ethan C.
Validated Reviewer
Verified Current User
Review Source

"Excellent and extensible build tool"

What do you like best?

An invaluable tool that ties in perfectly with GIT, local build repositories and makes it easy to visualize what's happening. You see a history of your builds, configure and control nodes to use for builds, its a great flexible tool. Another powerful use of jenkins is for kicking off fitness tests that test your app/site, which you can then tie to alerting when things break.

What do you dislike?

Some of the settings are buried within the UI, takes some time to get familiar with, but worth the investment.

What business problems are you solving with the product? What benefits have you realized?

We use it for build automation, its great for kicking off builds via changes in SCM's

Jenkins review by Judy (Morgan) L.
Judy (Morgan) L.
Validated Reviewer
Verified Current User
Review Source

"Powerful and flexible"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Filipe O.
Filipe O.
Validated Reviewer
Review Source

"The best value you'll get for a CI software"

What do you like best?

Jenkins is very extensible with a lot of ready to use plugins. Although it takes some time to get along with it, you'll not regret because it's free. It really worths the try.

What do you dislike?

The user interface is ugly and confusing (though you can lower the frustration by adding themes). Really. Jenkins UI and UX are no match for any of its competitors. It takes a lot of time to get along with it.

Recommendations to others considering the product

Don't do it in your environment at the first time. Don't try to setup your behemoth project at the first time. Don't install a lot of plugins right away. Start small so you can learn it properly.

What business problems are you solving with the product? What benefits have you realized?

I've implemented Continuous Integration and Continuous Deployment for my early stage startup. In such stage we need to save the best we can, and Jenkins really worths the cost of learning so we can work the agile way from day one.

Jenkins review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Reliable and extensive integrations"

What do you like best?

I really like Jenkins and think it is a great tool! The UI for Jenkins pipelines is very intuitive and clearly conveys the current stage of the pipeline and failure stage.

What do you dislike?

Jenkins relies on plugins for much of the extended functionality. There are many plugins that provide functionality that is simple and common enough that it should be base functionality.

Recommendations to others considering the product

Provide more functionality out-of-the-box rather than relying on plugins.

What business problems are you solving with the product? What benefits have you realized?

Build docker images for environment for 200+ microservices. The Jenkins pipelines help reduce the amount of redundant manual work for building, deploying, and running tests.

Jenkins review by Jonathan Y.
Jonathan Y.
Validated Reviewer
Verified Current User
Review Source

"Fantastic ecosystem, cross-platform support"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

Building software projects and running periodic tasks using Java, NodeJS, batch scripts, and other tools.

Jenkins review by Siôn l.
Siôn l.
Validated Reviewer
Verified Current User
Review Source

"Jenkins is highly customisable and good for testing and CI for private repositories."

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Steve F.
Steve F.
Validated Reviewer
Verified Current User
Review Source

"Flexible, well-supported, enterprise-class CI available for free."

What do you like best?

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?

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 the product

Try it out. Don't be scared off by a slightly outdated-looking UI - this is a very advanced and modern application.

What business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Ananyo S.
Ananyo S.
Validated Reviewer
Verified Current User
Review Source

"Integrated build system for your projects"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Shayne V.
Shayne V.
Validated Reviewer
Verified Current User
Review Source

"Jenkins Review From A QA Engineer Perspective"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Denis B.
Denis B.
Validated Reviewer
Verified Current User
Review Source

"An old friend is better two new ones"

What do you like best?

* 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?

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 the product

Jenkins worth to try, but it will require some time from your build engineer to make it what best suite to you.

What business problems are you solving with the product? What benefits have you realized?

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

Jenkins review by Danny G.
Danny G.
Validated Reviewer
Verified Current User
Review Source

"Vital tool in my CI/CD toolbox"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Imran H.
Imran H.
Validated Reviewer
Verified Current User
Review Source

"used it extensively for our distributed CI system. also worked on plugin development"

What do you like best?

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?

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 the product

use the latest workflow strucuture as suggested by cloudbees .

What business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Review Source

"Jenkins the Tool for CICD Pipeline"

What do you like best?

I have started using Jenkins since last 1 year and since then its easy to do build and deployment on required windows, Linux, Unix servers. We just have to configure the job as per our requirements and then its easy by just one click build and deployment. For my current project, we have created a complete CICD pipeline where in we build from develop branch and deploy to production with passing requirements like SONAR analysis of code, uploading package to Nexus Repository,checking on test cases using Jasmine test & nUNIT test and also staging packages to stage location and then robocopy to destination. It has made a lot of my efforts easy with one click execution.

What do you dislike?

The only issue I face in Jenkins is getting the slaves for my jobs. We are not sure it is Jenkins issue or the server issue at our side. But with my experience of using Jenkins i can say out of 10 we face 4 times slave issues and our Job get stuck because of it.

Recommendations to others considering the product

Use it as it is easy to learn. Lot of guidelines on the internet on how to use it, how to build a job and create a pipeline. it will make you work easier for build and deployment.

What business problems are you solving with the product? What benefits have you realized?

Earlier without Jenkins we were manually deploying to our servers and there were a lot of chances where we would miss one or the other thing in deployment. Now with Jenkins and with one click deployment our process has become easy and error free and less human errors and also saves deployment time.

Jenkins review by User in Computer Software
User in Computer Software
Validated Reviewer
Verified Current User
Review Source

"Great for continuous integration"

What do you like best?

I like that the configuration is very simple and to the point. It also has the ability to integrate with other software via plugins. Each of those plugins has sufficient documentation and examples on how to use.

What do you dislike?

It could improve on its analytics. There also should be a way to track changes on it. Many a times I found that the configuration on the jobs were modified but we didn't know who changed it and what was changed exactly.

What business problems are you solving with the product? What benefits have you realized?

We're trying to achieve continuous integration and deployment using jenkins. We can automate a lot of the tasks using this tool.

Jenkins review by Yukti A.
Yukti A.
Validated Reviewer
Review Source

"good to run scripts and tests; has lots of integrations"

What do you like best?

It has a lot of integrations, with arc, git, and slack. when working in large code bases, it's helpful to run the tests on the cloud since it's difficult to do so locally.

What do you dislike?

sometimes confusing to set up. the UI is a bit outdated. sometimes things crash and restarting will make tests pass. there's a few other bugs where some settings get overridden for each diff, so they need to be manually adjusted.

What business problems are you solving with the product? What benefits have you realized?

build automation, run scripts and tests before allowing new code to be merged into master

Jenkins review by Jonatan Ezequiel S.
Jonatan Ezequiel S.
Validated Reviewer
Verified Current User
Review Source

"Really good product"

What do you like best?

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?

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 the product

If you want to deliver a project to a CI without configuration dealing Jenkins it's not correct for you.

What business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Gurusharan S.
Gurusharan S.
Validated Reviewer
Review Source

"Automate your Deployement with Jenkins"

What do you like best?

Jenkins is the most used tool for build automation. You just need to push code on your git repository, Then jenkins will update code on your servers as your requirements. For basic tasks, you can use shell scripting, For complex use-cases jenkins pipeline is very good. It is highly flexible and reliable.

What do you dislike?

I don't have any dislikes for jenkins, you can think of any thing, Jenkins will certainly have solution for it.

What business problems are you solving with the product? What benefits have you realized?

You can save a lot of time by automating your deployment process using Jenkins.

Jenkins review by Eric M.
Eric M.
Validated Reviewer
Verified Current User
Review Source

"Your new, hardest-working teammate."

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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!

Jenkins review by Joe D.
Joe D.
Validated Reviewer
Review Source

"Like a good butler, Jenkins is there!"

What do you like best?

It runs the show! Let Jenkins do all the things for you. Easy to get running. Easy to get jobs going. Hook jobs to events, or make generic jobs that people can use when they desire. Then, stand by and watch the good reports come down the pipe. You can easily improve your development process with Jenkins. It is the gold standard.

What do you dislike?

Haven't really found anything that I dislike. It's so well used and supported that it's easy to find the help that you need.

Recommendations to others considering the product

Follow best practices. And just use it. It makes your life easier. You want and need to do continuous testing and building, so use the tool that is the best for that.

What business problems are you solving with the product? What benefits have you realized?

Continuous integration testing. Release testing. Sandbox testing. Anything and everything.

Jenkins review by Administrator in Hospital & Health Care
Administrator in Hospital & Health Care
Validated Reviewer
Verified Current User
Review Source

"Jenkins makes it easy"

What do you like best?

The ability to push code at 4 am with a push of a button. It makes it easy to set up the servers as slaves and they can be updated at the same time.

What do you dislike?

If you use batch files for executing and copying files it can get real messy really quickly! Batch files tend to not run as intended and can cause problems pushing updates.

Recommendations to others considering the product

It is a powerful software if used as intended.

What business problems are you solving with the product? What benefits have you realized?

It helps streamline the process of pushing code with an ease. It makes our production push faster and introduces less bugs.

Jenkins review by Arif K.
Arif K.
Validated Reviewer
Verified Current User
Review Source

"One of the best tool for build automation"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Pranathi V.N V.
Pranathi V.N V.
Validated Reviewer
Verified Current User
Review Source

"Best build automation tool"

What do you like best?

Speed of builds. Integration with slack. Ability to set up nightly builds i.e different kind of triggers. Both plugin based and grovy/java based access to the build triggers. Easy to setup pardllelizable tasks

What do you dislike?

Interface is not as fancy, but it doesn't have to be. Documentation and support could improve by a lot

What business problems are you solving with the product? What benefits have you realized?

Building nightly, Continuously testing our developement much mire faster than circle. Ability to control builds inhouse machines

Jenkins review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Verified Current User
Review Source

"THE GOTO Tool"

What do you like best?

Pretty easy to set up and get going, very extensible and reliable.

What do you dislike?

User Interface is ugly and sometimes downright limiting.

Recommendations to others considering the product

If you are working in primarily Java, use Jenkins for sure.

If you want an easy to use and widely supported devops server to start out with, use Jenkins for sure.

If you want to easily coordinate running software on multiple systems, use Jenkins for sure.

If you want highly transferrable skills, learn Jenkins.

If you want a very friendly license, use Jenkins.

If you enjoy tinkering, you'll enjoy Jenkins.

This runs anywhere Java runs.

Have a secondary testing install somewhere else, some plugins are old and bad and do not work with others. You need to test things before sending live against a shop already relying upon the Jenkins instance and you do not want to be that guy.

Some nice, advanced features are just hard to learn. The Pipeline feature is an example of this. DO learn Groovy enough to accomplish useful things with Jenkins. Do expect Pipelines to be hard to learn well.

What business problems are you solving with the product? What benefits have you realized?

We do QA Automation and this we use for scheduling jobs and tests and getting results out

Jenkins review by Mykel A.
Mykel A.
Validated Reviewer
Verified Current User
Review Source

"The way we do CI (at the moment)"

What do you like best?

We're primarily a maven build shop, so our builds tend to "just work" inside Jenkins.

The plugin architecture is weird but there are a huge pile of them. I've only rarely had to implement my own.

We frequently use Jenkins to provide validation of builds that are too complex to do locally,

What do you dislike?

The interface is very 2005. Better than Bugzilla, at least. The credential management is pretty oddball, but can be figured out.

The quality of 3rd party plugins varies widely from crap to awesome.

Recommendations to others considering the product

Make sure your build tools are supported.

User management can be very challenging.

What business problems are you solving with the product? What benefits have you realized?

We're looking for continuous integration testing with multiple slave machines of different capabilities. Jenkins gives this to us essentially for free. We tried Cloudbees but it was difficult to migrate our mechanisms to their hosted environment.

Jenkins review by Amir S.
Amir S.
Validated Reviewer
Verified Current User
Review Source

"Your friend, if you are a hacker"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Aniruddha B.
Aniruddha B.
Validated Reviewer
Verified Current User
Review Source

"Excellent - easy configuration"

What do you like best?

* Easy to configure/ set up.

* Creating and deploying builds is easy in the interface.

* No installation costs

What do you dislike?

* 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 the product

* The product is useful with its build features and easy configuration setup.

* Learn the work flow structure and stay ahead of the game.

What business problems are you solving with the product? What benefits have you realized?

* 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.

Jenkins review by Administrator in Real Estate
Administrator in Real Estate
Validated Reviewer
Verified Current User
Review Source

"I lub jenkins"

What do you like best?

Automating my workflows, from deploying code to having jenkins tasks that integrate with our health monitoring to fix outages.

What do you dislike?

Finding examples of different workflows for different business needs. I work for a small Marketing agency with an internal dev team. I don't think we're the average jenkins users. Most people i know using jenkins are working for larger companies or startups, primarily as a devops team. Learning new features sometimes seems unintuitive.

Recommendations to others considering the product

If you are debating between different CI/CD tools, look no further. You'll be sorely disappointed that you used a hosted version of other tools when you begin to realize how you can use Jenkins for non CI/CD tasks. Automation is the future and Jenkins is the forefront.

What business problems are you solving with the product? What benefits have you realized?

Continuos integration and deployment of our applications. Automated tasks to fix infrastructure or applications triggered by our monitoring and metrics platforms. The great part is how easily jenkins integrates with all of our different tools, bitbucket, nagios, slack, and others. We can build our code, deploy it, and automatically notify product owners and QA teams that the code has been deployed for a specific project.

Jenkins review by ankit k.
ankit k.
Validated Reviewer
Verified Current User
Review Source

"This is Perfect for CI and CD."

What do you like best?

I t feels like I do not have to do anything for integration or build.

It is something we call as fire and forget.

We have a code in bit bucket and configured the job in jenkins and now the whole code works just perfect.

What do you dislike?

A little tricky to understand the functionality , but you can learn it its worth.

Recommendations to others considering the product

Recommended

What business problems are you solving with the product? What benefits have you realized?

There is nothing which we were trying to solve but yes it eases up your other processes

Jenkins review by User in Internet
User in Internet
Validated Reviewer
Verified Current User
Review Source

"Free, Simple and Fun"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Guillaume A.
Guillaume A.
Validated Reviewer
Review Source

"Really straightforward & easy to setup"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.....)

Jenkins review by Administrator in Information Technology and Services
Administrator in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Wonderful piece of software"

What do you like best?

Jenkins is possibly the most versatile software when it comes to DevOps. Installation is a breeze and there are thousands of plugins that allow you to integrate Jenkins with pretty much anything under the sun. We were able to integrate Jenkins with our in house HP Performance Center, Qualilty Center/ALM and Selenium with equal ease.

What do you dislike?

Documentation can be a bit hazy. You are dependent on forums for more issues.

Recommendations to others considering the product

Anyone considering DevOps should consider Jenkins as their first stop! Being free, you are not going to lose anything trying it!

What business problems are you solving with the product? What benefits have you realized?

Automation! When it comes to automated / integrated testing tied to code checkins, Jenkins definitely beats the rest of the crowd

Jenkins review by Anderson G.
Anderson G.
Validated Reviewer
Verified Current User
Review Source

"Very flexible and customizable CI software"

What do you like best?

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?

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 the product

Keep it updated and use as less as possible plugins. They are great, but only install what you really needs.

What business problems are you solving with the product? What benefits have you realized?

I'm using it as a platform for our deploy server, where we build our packages, publish and run backup tasks.

Jenkins review by Curtis R.
Curtis R.
Validated Reviewer
Review Source

"Fantastic CI Solution for On-Premise and the Cloud"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Review Source

"One of the best build automation software I have ever used"

What do you like best?

Jenkins is one of the best build automation tool I have ever used.

- Open Source, can be easily extended as per the needs.

- Hundreds of plugin available.

- Extremely easy to configure.

There are several useful plugins available for all the needs, i.e. code coverage, findbugs and many more useful plugins. The product is very much stable and provide a better experience,

What do you dislike?

There are not so many dislikes I have for Jenkins, however few things can still be improved:

- UI can be improved, however one can always extend their code as per the need.

- It becomes little slow when there are several jobs running simultaneously, however there are ways to optimize.

Recommendations to others considering the product

I would highly recommend Jenkins for the teams who wants to automate their manual process. The setup and configuration is easy and does not require too much of efforts. There are plenty of tutorials available for the same.

We were able to solve lot of issues through Jenkins. It also provides you graphs and visual representation of the generate reports. We used Jenkins from build process to running the automation test cases.

What business problems are you solving with the product? What benefits have you realized?

We used Jenkins in our team to automate the build process and for continuous integration.

Jenkins review by Consultant in Information Technology and Services
Consultant in Information Technology and Services
Validated Reviewer
Review Source

"Great for build automation"

What do you like best?

the ease of configuring the automation builds. Once Jenkins server is set up and the builds are configured, it is very straightforward for the development team to run the builds as and when required. The 'no login' required feature is also great. The auto scheduling works very well at all times.

What do you dislike?

Looking into the console output of any build requires more than 2 clicks. This is what I dislike the most when i compare features from the last tool we used to Jenkins

Recommendations to others considering the product

jenkins is very easy to use for a development team on a recurring basis. with no user logins required, it enables everyone to fix any build issues at any given time. The build grouping it offers is useful so as to ensure that all related builds belong together. The build configuration is very easy to understand and easy to update. The auto scheduling works great and the build server is never overloaded.

What business problems are you solving with the product? What benefits have you realized?

We have ensured that our SYS testing environments (6 in total) are up to date every morning with the latest changes that the developers checked in

Jenkins review by Pavel S.
Pavel S.
Validated Reviewer
Verified Current User
Review Source

"Day job CI"

What do you like best?

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?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

Automated testing and deployment to certain environments; rarely need to do that manually anymore.

Jenkins review by Administrator in Information Technology and Services
Administrator in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Amazing e complete service for continuous integration."

What do you like best?

- All variety of plugins and features available.

- Easy to install

- Huge and active community.

- Complete support for Java and Groovy, my main languages for development.

What do you dislike?

- The need of a dedicated server and some linux skills to install the service.

- Concerns about the server security and maintenance.

- Some build sequences of build, deploy and archive artifact could cause some confusion if you try to use different jobs for each step.

- Warning massages sometime are needed to avoid deploys by mistake in production environment instead of homolog by example.

Recommendations to others considering the product

If you have experience with cloud linux servers and some skill to install a service on then, you really should try Jenkins. After the first project is setup all the others will probably take 5 minutes to setup em run.

What business problems are you solving with the product? What benefits have you realized?

- All projects from my company are builded and deployed with one click (maybe two) with Jenkins, with this is possible to avoid human errors and gain a precious time with dedicated link direct with my target servers.

- All this is much faster and reliable with automated processes.

- No dependency to a specific person and machine when you must build and deploy, mainly in some kind of emergency in the last minute.

Jenkins review by Icyleaf W.
Icyleaf W.
Validated Reviewer
Verified Current User
Review Source

"Jenkins with Mobile App Build and DIstrubtion Review"

What do you like best?

one click install, has many plugins to use

What do you dislike?

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 business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Ashish M.
Ashish M.
Validated Reviewer
Verified Current User
Review Source

"Jenkins is best opensource CI tool so far"

What do you like best?

Best is this is opensource and large community is following this.

UI is very simple and admin things are easy to follow.

Never ending plugins are available. You just think what you want to do and probably you will get a plugin.

Initial setup of jenkins server is very easy.

Lot of documentations available to help deploy with tomcat.

Adding client nodes is super easy. Just fill in minimum details and you are done.

Configuration page is very versatile and gives you lots and lots of options to use for your job.

What do you dislike?

I experienced lot of HEAP space issues. Many times i have fixed that with more heap space in CATALINA, but i think Jenkins should be able to handle it on its own.

Also, I found some lack of documentations on plugins. Jenkins is easy to setup but later on it takes time to use some complex plugins which are not very straightforward and need some pre-configuration in administration.

Recommendations to others considering the product

Its opensourse and once you started with this and realize its power, you cant stop using it

What business problems are you solving with the product? What benefits have you realized?

Daily builds, nightly builds, automation testing, other utility jobs

Jenkins review by Rubén S.
Rubén S.
Validated Reviewer
Review Source

"CI solution for my current company"

What do you like best?

It is highly configurable to build programs developed in different languages, and different build managers. Currently we are building more than 30 projects mainly in Java and Groovy languages. Also we are using it to automate the creation of forks for the projects.

What do you dislike?

If you have a lot of builds configured in the same server the builds can be too slow.

Sometimes it is difficult to find where a build has failed, because you have to manually check the console output.

What business problems are you solving with the product? What benefits have you realized?

We use Jenkins to build all the different projects as well as the CI solution. We run our unit and functional tests and make check style and sonar validations.

Jenkins review by Steve H.
Steve H.
Validated Reviewer
Verified Current User
Review Source
Business partner of the vendor or vendor's competitor, not included in G2 Crowd scores.

"Jenkins is one of the better-known self-hosted java-based CI servers"

What do you like best?

Jenkins was forked from Hudson, one of the early CI servers. At the time Hudson came out, Cruise Control was what most were resigned to, which required a lot more care and feeding. For its part, Hudson is very simple to set up, in theory; just run the WAR file. It works out of the box, has probably the largest user base of the self-hosted solutions, and plugins for most everything you'd want to integrate into your workflow. Or you can write your own plugin, using any JVM-friendly language (it's not just for Java anymore).

Building custom forms in order to provide options for automated builds is fun and easy.

Very configurable by itself. If you need to cobble something together quickly, you can always drop down into a shell script.

No doubt, hosted solutions like Solano and Travis are sexier. But they also cost money, and by definition they have eyes on your data. That rules them out for shops where HIPPA or other security policies have to be followed.

What do you dislike?

The plugin ecosystem is poorly managed. It's unclear which combination of plugins are safe to use together. Many are readily available for inclusion, but haven't been supported in years, or will only work on older versions of Hudson.

Given this, sometimes it's NECESSARY to cobble something together.

Recommendations to others considering the product

If you require a self-hosted solution, Hudson will likely have what you need, but it may require a few trips to the forums. Happily there's still a large user base. OTOH, TeamCity is free for smaller teams, and may prove easier to set up and maintain.

What business problems are you solving with the product? What benefits have you realized?

Other than standard CI workflows, I used Jenkins at a financial services company as a means to kick off compliance tests. Non-technical users had an easy HTML form where they can select they combinations of tests they want to run, the locales to run them in, the environment to target the tests against, etc. Artifacts such as screenshots and audit logs are readily available and preserved in a way that makes sense to the business. Tests are run on a schedule, or before a big release.

Jenkins review by Dmitry B.
Dmitry B.
Validated Reviewer
Verified Current User
Review Source

"Jenkins is not perfect, but it has best pipeline view plugins"

What do you like best?

- Ease of use

- Variety of plugins

- Rich plugin API

- Pipeline support (build pipeline, delivery pipeline)

- Job parameterization

What do you dislike?

- No job templates

- Poor plugin compatibility (if you have a working configuration with 100+ plugins you probably won't be able to upgrade without breaking anything)

- Performance issues (1000+ jobs)

Recommendations to others considering the product

Jenkins has less support from core developers than commercial products.

However, it has large community and your problem will likely already have a solution if you use stable version of Jenkins and plugins.

What business problems are you solving with the product? What benefits have you realized?

- Build Java projects

- Build Kotlin projects

- Build Android projects

- Run automated tests

- Run performance tests

- Run static code analysis

- Produce various reports

Jenkins review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Verified Current User
Review Source

"Nice Build and Integration"

What do you like best?

Build Automation and Continuous Integration.

What do you dislike?

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 the product

For who handles more than 20 machines, you should try it.

What business problems are you solving with the product? What benefits have you realized?

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.

Jenkins review by Guiomar T.
Guiomar T.
Validated Reviewer
Review Source

"Powerfull OpenSource CI Server"

What do you like best?

It is highly configurable, and it has many plugins that helps you to integrate it with many tools.

It is possible to set jobs to automatise builds, tests, deploys... and many other processes within the different environments like development and production.

What do you dislike?

Some of the plugins are discontinued.

The integration with docker-swarm is not set (or at least I have not seen how)

There isn't a hosted Jenkins service, so it is necessary to own a machine (physical or virtual) to launch it.

What business problems are you solving with the product? What benefits have you realized?

We are using it to test component integration. Launch unitary tests and integration tests.

Deploy components.

Jenkins review by Ken Y.
Ken Y.
Validated Reviewer
Review Source

"Great ecosystem w/ lots of plugins"

What do you like best?

Jenkins has the largest set of 3rd party tools for an open source project. It also has builds available for a lot of different platforms. The build environment lets you define setups easily and above all makes debugging them simple. Because it runs on OSX, you can do IOS builds as well as use Vagrant/Virtualbox to test out server builds.

What do you dislike?

Some of the web admin pages are bit quirky when you add plugins so you can't figure out where the sections for each plugin are. Connecting multiple Jenkins servers to the cluster is also a bit difficult. There's no simple way to tell it to test all your source code branches.

One other thing that's confusing is on OSX, there are multiple ways to install it...via homebrew or as a separate app, etc.

Recommendations to others considering the product

Set Jenkins up on a separate virtualbox or docker machine so it's easy to move it to another system.

What business problems are you solving with the product? What benefits have you realized?

Jenkins was used to do build/testing automation testing. The build of each version of code was validated quickly every time someone checked in code because unit tests were also done on the build server. Server builds were validated on the server by using vagrant to build up a copy of the server from scratch and run unit tests against it.

Jenkins review by Timothy S.
Timothy S.
Validated Reviewer
Review Source

"The Build Tool for Today"

What do you like best?

Anything is a job, everything is a job. Tons of plugins, just configure a few basic things, add some parameters and it runs. Very easy to hook to Github, other servers. It is very easy to run static code analysis tools like PMD and CheckStyle.

It can also run all your JUnits and publish the HTML reports and code coverage.

What do you dislike?

It be default does not have great security and requires the install and configuration of a lot of plugins to be really useful. It would be nice if there were some wizards and more templates to copy jobs from. These are minor, but would be great.

Recommendations to others considering the product

Try it on your pc, it's easy to download and install as it's a Java application. You can also install it and try it on OpenShift.

Once you try it and have it automatically build and deploy things from your github you will be hooked. So easy and saves you a step. Just commit something to your git repo and it builds.

What business problems are you solving with the product? What benefits have you realized?

The tools is without equal, there are others and many more expensive tools. But this is the gold standard, you just have to setup a job and it runs itself. Great replacement for cron as well.

Jenkins review by Bill B.
Bill B.
Validated Reviewer
Verified Current User
Review Source

"CC Jenkins Review"

What do you like best?

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?

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 the product

Use it. Keep your developers doing what they do best.

What business problems are you solving with the product? What benefits have you realized?

Automate menial tasks including unit tests, test environment build, and final deployment of code changes.

Jenkins review by User in Insurance
User in Insurance
Validated Reviewer
Verified Current User
Review Source

"Love using Jenkins as a CI Tool"

What do you like best?

I like how easy it is to use and how clear the dashboard is.

What do you dislike?

The UI is very out of date, it has been updated recently but is still lacking.

Recommendations to others considering the product

The latest version has pipeline management for CI/CD which is great.

What business problems are you solving with the product? What benefits have you realized?

We use Jenkins as an automated continuous integration tool to automatically deploy to a environment upon commit, nightly or ad hoc. We also use it to automatically run tests.

Jenkins review by Roberto O.
Roberto O.
Validated Reviewer
Review Source

"Build all the things1"

What do you like best?

Jenkins is free, open and has a very huge community behind its back: if you have an issue, you can bet on the fact that there is someone ready to help you . There is no way you have to give up on your plan of building everything with Jenkins as this would not happen. Rock solid, open and spread, One of the best CI ever.

What do you dislike?

Building for the Android platform is easy, once you get up and running. And this is the pain point for most of the user: setting everything up (included the Android SDK) can be hard and time consuming but, if you do not desist, you will surely manage and be able to use Jenkins at the full potential for your builds.

Recommendations to others considering the product

If you need an open source build system and are not scared from the (maybe) time consuming activity of configuring your builds for each and every platform you develop for, Jenkins is your tool. No one can match its versatility, its reliability and the community behind this software. You will most certainly face issues, but I'm positive about the fact that someone will be ready to help you finding the right path to your solution!

What business problems are you solving with the product? What benefits have you realized?

In both my previous employments, we were using Jenkins as both CI and Build Automation: I used it with Ant and with Gradle and the tool was really doing its job. Nightly builds, test runs and APK archiving, all automatically whenever you needed, with a release build always ready to be served.

Jenkins review by David H.
David H.
Validated Reviewer
Review Source

"Jenkins: IndieDev or Team - a tool for making pro software"

What do you like best?

Extensibility; there a tool for practically every development and build automation you can think of.

What do you dislike?

Can bit initially hard to set up if you're not familiar with all of the supporting tools it needs for your given task; if you're doing iOS develop there is a lot more effort required to get everything integrated with Xcode, build profiles etc.

Recommendations to others considering the product

Make sure you really understand your development & deployment process before you attempt to bring Jenkins into the mix. if your current system it heavily tied to a single user or group of users you will really want to break those cycles before trying to use a CI system like Jenkins. Alternatively if you want to find all the places your build process will break and all the holes in your deployment system trying to dive into Jenkins will do that for you. Be prepared to spend a couple of weeks working out the kinks and adjusting your development regime so that your devs don't break the build process over & over not even talking about failing tests here... just the building process part).

What business problems are you solving with the product? What benefits have you realized?

Build automation for iOS applications.

Jenkins review by Administrator in Information Technology and Services
Administrator in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Most customizable CI"

What do you like best?

In Jenkins we can do almost everything we want, you don't have restrictions like others CIs, for example, here we build and deploy mobile projects without restrictions.

What do you dislike?

Sometimes when we want to do simple stuffs we can't just click and it's done.

For example in others CIs, like Travis CI or Cicle CI we can add a yaml file and just wait for the configuration, in Jenkins we need to setup the project, but at least we don't have restriction about what we can do

Recommendations to others considering the product

Jenkins can solve all of your problems to automate, integrate and deploy/delivery, but you'll need to study the documentation.

What business problems are you solving with the product? What benefits have you realized?

We are using jenkins to build mobile applications, using master and slaves for Android, iOS and Windows Phone. We also use for web applications and integration with AWS and deployment to mobile stores. The principal case that we need Jenkins to solve is to build iOS projects at Mac slave.

Jenkins review by Hélio C.
Hélio C.
Validated Reviewer
Review Source

"Community Software. Also known as Hudson"

What do you like best?

Very customizable tool to keep your coding working. Fits well for teams of any size. By running your source code automated tests, you and your team can easily check if that modification will work into production environment as expected/designed.

Jenkins works with a vast range of languages such Java, PHP, Ruby, Python, Clojure, etc. There are tons of templates for each languages ready to be deployed into your own Jenkins' copy, avoid you to redo/search lots of its configurations.

Jenkins can runs Unit Testing, Functional/Acceptance/End-to-end tests; Frontend tests (Casper.js, Mocha, even Selenium is well supported).

There are tons of analytics plugins to keep your code quality based on language's metrics and best practices.

It's a free and open source software, so, you do not fear to get your code check by Jenkins.

Another import thing to mention is: Jenkins has at least 5 years of constant development by open source community. You can easily found Q&A on how to setup, configure, customize it on the Internet.

I do recommend if you have some deploy experience.

What do you dislike?

There is no SaaS version. You need to download and push to your own server to use it.

Also, it's a little bit ugly in a UI wise but it does not compromise in any way your daily basis use.

Recommendations to others considering the product

Price; Community support; Features

What business problems are you solving with the product? What benefits have you realized?

Continuous Integration; Continuous Deployment; Code Static Analysis.

Jenkins review by Gaurav S.
Gaurav S.
Validated Reviewer
Review Source

"Jenkins is good for automation of product, easy to setup and integrate."

What do you like best?

Jenkins have good documentation for setup. Jenkins work fine with rails app and easy to integrate. It's open source, good community. We can easy to run multiple build simultaneous. All about good to start with new app.

What do you dislike?

We try to "CI SKIP" option with rails app. PR but Jenkins not detect it. It always run test. Ci skip is use when only document type changes in a pull request. These kind of PR's have not need to run test. We also try plugins but Jenkins not work. I think it also take a lot of resource for testing a build.

Recommendations to others considering the product

For new project Jenkins is good startup integration. It have awesome features that are easy to use and good articles available on the web. When you have not any measure issue/problem with integration with it or automation process i can say it's good choice.

What business problems are you solving with the product? What benefits have you realized?

Easy to setup and integrate. When we haven't enough time simply use Jenkins. Also it's open source. Automation of app. is cool feature with Jenkins.