Jenkins Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
248 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.3 out of 101

Do you work for this company? Manage this listing

TrustRadius Top Rated for 2019

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (1-25 of 51)

Dodd Weisenberger profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
We use Jenkins as our build management software, and it is mostly used between the development and QA teams. We use it both in manual and automated builds. It allows the developers to work together and send a combined solution to the QA team. It also controls our versioning with minor builds and patches.
  • Automated build process
  • Great process control
  • Good notifications to groups
  • Can be difficult to configure
  • Not the best error reporting
Jenkins helps the flow of build from the development team to the QA team. Can be really helpful in doing continuous builds, but when this feature is turned on the development team must have great communication otherwise the risk of broken builds become very high. In the long run, we found it made things easier when we just pushed the build manually and appointed a team member the build master.
Read Dodd Weisenberger's full review
Richard Rout profile photo
Score 2 out of 10
Vetted Review
Verified User
Review Source
We used Jenkins as our build server to execute build jobs and automated tests. The whole of engineering used it to build jobs and checking build status. Ensuring their branches would successfully run tests before merging to the master branch. It was a cheaper alternative to non-open-source competitors since it was free.
  • Pluggable.
  • Extensible.
  • Large development community.
  • It's not cloud-based.
  • It can be hard to figure out.
  • High learning curve.
  • Have to maintain infrastructure yourself.
If you have a very complex set-up and want full control of your build and test servers, then Jenkins will work for you. It's free and allows you to deploy it on your own machines and set up everything exactly how you want it. You need to invest a lot of time and work. It's not good if you just want a simple build and any other cloud service will do it for you, cheap or free.
Read Richard Rout's full review
Erlon Sousa Pinheiro profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source
We're using Jenkins to perform part of our deployment pipeline. For our Development team, all the code tests are performed through Jenkins and on the DevOps side, all configuration management is performed by Jenkins integrated to Git, Puppet and Terraform. Also, their role on our day by day activities is quite important since we also use test routines on our configuration management pipeline and these tests are executed by Jenkins.
  • Manages the entire deployment pipeline, since the Git commit, going through several test types and the deployment.
  • Integrates with a bunch of other technologies.
  • Jenkins is amazingly flexible. The boundaries are your imagination. Just be ready to invest some time learning its several features.
  • Native integration with cloud providers. We still needing third-party plugins, that in some cases are not very efficient.
  • Needs better documentation.
  • A better front end. There is a lot of space for improvements in this specific aspect.
Jenkins has been serving us efficiently for a long time. It is quite reliable. Whether supporting developers work, DevOps work or staging/production deployment processing, Jenkins is a good choice. However, I believe there are some things that could be improved. When we need to execute parametrized builds, Jenkins could be more flexible in delivering us better screens (maybe something customizable) where we would insert variables to be used during the pipeline.
Read Erlon Sousa Pinheiro's full review
trang nguyen profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Jenkins as our main CICD server for multiple projects in our department and integrate Jenkins with our Gitlab source code repository and other tools such as SonarQube, Artifactory, Tomcat, Jboss, and Coverity. Our development team uses Jenkins jobs on every check-in code to run unit tests, scan code quality and run automation tests on every merge request before actually merging. Jenkins helps to increase our quality of product and eliminate most manual steps on deployment and integration.
  • Flexible to create jobs in freestyle or pipeline.
  • Supports various plugins to work with different programs such as AWS, Azure, Linux, Powershell, etc.
  • Gives you a centralized location to manage all project pipelines and build information.
  • Support various ways to trigger new jobs.
  • Allows us to edit and retain files in the server and not override by repository.
  • Support cluster to increase build performance.
  • Jenkins UI is too simple.
  • Does not provide a feature for backup and restore jobs.
  • Lack of authorization rule - We could not assign separate users or groups to separate views or jobs.
Jenkins is well suited when you need a CICD server to handle your compilation, building and deployment process, as Jenkins has many plugins and supports most script languages so it could handle almost any kind of project. In my department, before we start on a project, we define a clear strategy to use Jenkins, which task needs to be automated with Jenkins, which branch, and which module needs to be built with Jenkins and when we need to push a new version to Artifact and deploy to the server.
Read trang nguyen's full review
No photo available
October 17, 2019

Jenkins CI/CD

Score 8 out of 10
Vetted Review
Verified User
Review Source
Jenkins is the main workhorse supporting our build and deploy pipeline and is used by both developers and dev-ops alike. Jenkins provides a sort of single source of truth by running tests and verification steps to ensure that code going out to production is functional and safe. It also allows our team of over 100 developers to safely deploy production changes many times per day.
  • Highly configurable to individual needs
  • Many available plugins and integrations
  • Support for many different languages
  • UI feels outdated and unintuitive, especially to newer users.
  • User management is too simple.
Jenkins is well suited for large and/or distributed teams where synchronization of production releases is critical. Jenkins allows us to reduce risk of a bad release by gatekeeping deployment with a variety of useful checks and verifications. Jenkins also has a huge amount of community support, as well as a large variety of plugins and integrations. Integrations with GitHub and Slack are extremely useful for our team.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
Jenkins is used across various teams in our organization. It is an integration tool where we use the CI/CD pipeline for continuous deployments of our microservices. This tool makes life easy to automate the process of deploying services into all environments ( staging, production, and development environments). It uses in all development life-cycle processes including build, document, test, package, stage, deploys, static analysis, and publishing.
  • It is free of cost.
  • Easily configurable - Jenkins can be easily modified and extended. It deploys code instantly, generates test reports. Jenkins can be configured according to the requirements for continuous integrations and continuous delivery.
  • Easy support - Because it is open source and widely used, there is no shortage of support from large online communities of agile teams.
  • Most of the integration work is automated. Hence fewer integration issues. This saves both time and money over the lifespan of a project.
  • Jenkins management is generally done by a single user and that leads to tracking and accountability problems with the pushed code.
  • Jenkins doesn’t allow one developer to see the commits done by another team member, readily. This makes tracking the overall release progress a rather difficult job for larger projects. This can cause a lot of trouble with the release manager.
  • Jenkins doesn’t provide any analytics (there are plugins but they are not enough) on the end-to-end deployment cycle. This again goes back to the lack of overall tracking that contributes to the lack of analytics as well.
  • It is an open-source tool with great community support.
  • It has 1000+ plugins to ease your work. If a plugin does not exist, you can code it and share it with the community.
  • It is built with Java and hence, it is portable to all the major platforms.
  • Makes developers life easy.
  • Automate the build pipeline process.
  • Used for scheduling tasks and CRON jobs.
Read this authenticated review
No photo available
October 16, 2019

Excellent CI/CD tool

Score 10 out of 10
Vetted Review
Verified User
Review Source
We are using Jenkins for our CI/CD solution. It is used across all the departments in our org. we use Jenkins for various purposes. We use it deploying applications to various environments and taking the backups of the servers and restore them. We integrated Jenkins with various tools across the whole organization.
  • Scalable
  • Lots of plugin support
  • Integrates with almost every tool
  • Sometimes a bit slow
Jenkins is the best CI/CD tool, it integrates with most other tools. it has lots of support for various plugins. Jenkins with DSLs and Jenkinsfile it can be extremely configurable. We can automate the whole build from a Git push to prod deployments.

For microservices we have a bit better tools then Jenkins.
Read this authenticated review
No photo available
Score 6 out of 10
Vetted Review
Verified User
Review Source
[We're] Using Jenkins for CI/CD automation and enforcing quality gates.
  • Rich plugin ecosystem
  • Infinitely extendable via custom configuration
  • Scalable thru multi node architecture
  • First-class support for docker containers
  • More modern runtime, without the Java overhead
  • Better isolation for plugins via containers
The industry workhorse due to its swiss-army-knife abilities, but lacks in some modern features like first-class support for docker containers.
Read this authenticated review
Dylan Cauwels profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Jenkins to automate our CD/CI jobs across a variety of applications. It is used by our QA teams to set up automatic testing for software deployments, and by our deployment team to deploy those applications in an automated fashion. This tool is crucial to any DevOps setup and will allow your teams to deploy as often as they would like with minimal effort or employee intervention.
  • Automatic jobs: there are infinite possibilities when it comes to Jenkins. You can run code against any testing suite you can imagine or conjure up. You can deploy applications at any time anywhere, automatically with no human intervention. If a certain stage fails, it will notify the team and your sysadmin of the issue so you can resolve it as quickly as possible
  • Automatic rollback: because of how Jenkins works, it can hold off publishing code and integrate locally to run QA procedures before pushing to deployment. This means that bugs are caught before your servers are updated and prevents a faulty program from affecting your downtime in the first place. Its a game changer for high availability.
  • Very un-intuitive UI can be very confusing for first-time users. It will take a decent amount of time to get any new users comfortable with using the tool
  • It is open-source, but because of this, there is not a lot of support out there for Jenkins-related issues. Because of the possibilities of Jenkins with plugins and customization, there is a decent chance any errors you encounter will be the first of their kind and will have to be solved by you and you alone.
Well suited for any environment that needs to be as automated as possible and is built around the DevOps philosophy. Also, perfect on any cloud infrastructure system as it allows for considerable customization for any type of setup. It allows for applications to be developed in a fast, reliable manner by cutting out the tedious process of integration or basic QA testing. I legitimately cannot think of a scenario where Jenkins would not be useful in improving your software workflow.
Read Dylan Cauwels's full review
Hung Vu profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Jenkins as CICD server for our java application, We use both freestyle and pipeline project to have full lifecycle build from compile, unit test, code scan, build, deploy and run automation, performance test.
We use the freestyle and pipeline and they give us flexibility on what action we expect, we just compile and run unit test on every code checking, build a new snapshot artifact and deploy to test server then perform smoke automation test when merge to master, and run full automation test.
  • Installing Jenkins is easy, just download the software and few clicks or use command line, chef cookbook, Ansible task... which it already supports. Configuring Jenkins is simple for adding users, variables, plugins
  • Integrates well with other DevOps tool such as Maven, Gitlab, SonarQube, Selenium...
  • Easy for debugging and customized jobs
  • The documentation is clear and rich
  • Has many plugins
  • Great support from community
  • The dashboard is hard to manage when we have many jobs
  • Add some default plugins in Jenkins original package
Jenkins works well for centralizing CICD server in almost any scenario, from simple to complex systems, but you will need a dedicated server for it.
Jenkins is simple to learn so you could start without experience and it is free
If your organization already uses Gitlab, GitHub or Bitbucket you could use their CICD pipelined instead of Jenkins.
Read Hung Vu's full review
Mark Carpenter profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
Jenkins is our standardized build tool for all our software teams. It has allowed us to move to a standardized continuous integration development cycle rather than the ad-hoc build and deploy structure that was used in the past. Having the ability to manage all our builds from a single web platform has been great for the management of our build process. We now have the ability to easily pull build logs and to determine where individual builds we're deployed. Jenkins has been highly beneficial for our company.
  • Manage continuous integration. It can be set up.
  • Allows a single point of access for all our companies build information.
  • It is also highly configurable and allows our individual teams to customize the builds as necessary.
  • We have had some trouble with using Ansible with Jenkins to allow a 'pipeline' build. This points to a potential area Jenkins could improve by allowing a clean way to define build pipelines. It has the ability to define promotions to specific environments but the UI for that feature is not intuitive.
  • There were a few examples where saving build configuration changes would not actually save the changes.
  • Jenkins is a great tool, but the UI for the list of projects becomes hard to navigate when you have a large number of projects. It could use an updated design.
Jenkins is well suited to be used in any build use case. I consider Jenkins to be the gold standard for build tools and should be the primary choice for any build unless there are mitigating circumstances that require another tool.
Read Mark Carpenter's full review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
We use this technology throughout the company. Most of the time we integrate this with Git. Just by installing a Git plugin to the dashboard we are ready to rock and automate. We do the following process (this step by step guide will brief you more on our work): 1. Install and Integrate Git plugin with the dashboard of Jenkins (localhost:8080), 2. provide the URL/repository URL, 3. git pulls request so as to sync save all data to Jenkin workspace, 4. go to SCM, and select Git in freestyle project, 5. execute the operations and some batch commands, and 6. you are done! Now you are ready to automate your tests (Plugin wise) and debugging. We mostly use mailer application which triggers a mail to all the recipients when our production code builds successfully.



  • Real-time deployment and synchronization.
  • Automated Test cases and debugging.
  • We really like the tool/plugin called Mailer.
  • Best for DevOps. Reduced builds and processing time.
  • Once we organized a hackathon with our GitHub Storage. Jenkins was integrated at that time. We had a 20GB plan, but it oversized to 50GB. We had to bear a large sum of money which was unpredicted by our company. Being a startup we cannot bear such mistakes.
  • Jenkins cannot be easily studied and managed. We have to recruit personnel part-time for managing and servicing the server.
  • Though it is open source, there is no dedicated community driven forum or support. There are 3rd party discussion and support portals. Thus, we use Gitter always for debugging and solutions.
Jenkins is open source, thus has a large number of plugins rolled out already. All major VCS, SCM, Git, and Maven applications support Jenkins. They even support Docker which is trending in DevOps nowadays. It has more than 50 APIs and plugins to work on. Thus, it is always appropriate to have Jenkins when you have a distributed workforce and to sync with everyone. To avoid synchronization problems in the distributed workforce and development, we use Jenkins. Code pushed to VCS can be built over another system so as to deploy in the production/release.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
Multiple departments use Jenkins for deploying code to our dev/test/stage environments, and our ops team uses it primarily to deploy code to production endpoints.
  • Code package deployment. It wraps up and pushed out the code quickly and easily.
  • Good UI - verbose output is available, and there's an easy walk-through deploy process.
  • Multiple scripting language support - Jenkins can integrate PowerShell, Python, etc.
  • Documentation in the application itself is a bit thin.
  • Outside automation and integration aren't easily understandable. It would be nice to work in Ansible with Jenkins.
Suited for integration with GitHub, pulling on your master branch, wrapping it up into a deployment package, pushing that package out to an endpoint, and using scripting to update files. This process is primarily what we use Jenkins for, and it does this work well.
Read this authenticated review
Gabriel Samaroo profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
The engineering team at several of my previous companies used Jenkins as a Continuous Integration and Automation tool. We used it for managing deployments of our applications across various environments, as well as a way to manually run various operations, such as running Tests or Invoking scripts. Jenkins has some good user permissions, that allow us to delegate specific responsibilities to various individuals without worry of someone doing something they shouldn't be allowed to. The setup is quite simple, and the software is very intuitive to use.
  • Continuous Integration - A commit into a Git code repository can kick off a Jenkins job, which in turn runs a Test suite and an application deployment
  • History - View of everything that's been run and by whom
  • Flexible - Tons of plugins that allows Jenkins to integrate with other software/tools used in your companies tech stack
  • Sometimes, plugins are needed for even basic tasks. It would be nice if the base functionality included more, so you don't need to search and install a bunch of plugins.
  • The UI can be a little clunky. Although there is a Blue Ocean project that rethinks the UI of Jenkins and is much nicer.
  • While the user management works, it is a little naive. You cannot do things in bulk or things that are TOO complex.
Jenkins is a great tool for teams looking to build automation and continuous integration into their development workflow. It is very easy to setup and works of all the major Operating Systems. Anyone can learn to use Jenkins because the software is quite intuitive. There is also a huge community surrounding Jenkins, which makes learning resources very easy to find.
Read Gabriel Samaroo's full review
Ramendra Sahu profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source
This tool made the development flow fluid. Standout features are the continuous integration and a variety of support offered for creating packages for a number of technologies like, Java, C#, C++, etc and across multiple platforms that makes releases easier for faster roll out of business functionalities . It also has hundreds of plugins that can help you setup continuous integration and continuous delivery tool chain in quick time. You can easily scale out Jenkins across multiple machines, and support simultaneous large number of builds, tests and deployments across multiple platforms.
  • There are plenty of plugins available which helps us automate most of the jobs.
  • You can do anything with Jenkins as there are a huge number of community plugins. There is a learning curve of course but after you've mastered it's quick sailing.
  • The ability to schedule jobs on the go for your software build is very useful.
  • I particularly don't like the user interface. There's a lot of scope for improvement. I would actually say a complete revamp is required.
  • It is quite time consuming and not intuitive to create a job.
  • The new build pipelines feature is good but needs to be refined and issues needs to be ironed out.
It supports a rich set of plugins. The job configuration history plugin, for example, allows you to see history of past builds. Features are constantly getting enhanced with each release. Great active community support, which can help you if you are trying to do something new. Better than a lot of peers available in market. GitHub integration and pull request and support for automatic code review are truly great features.
Read Ramendra Sahu's full review
Sagiv Frankel profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
Jenkins is as our R&D build and deploy pipeline.
It allows us to:
1) Run end to end and unit tests every time we push new code.
2) Compile and bundle our code.
3) Deploy images and containers it to our Azure servers (Kubernetes).
4) Give us a nice dashboard to view that status of the tests, builds, and deployment.
  • It is heavily used in the industry and it's open source. This is a huge benefit as there is a lot of learning material and more importantly there are many friends that can help you set things up correctly.
  • The new UI/UX design is very user friendly and gives you good viability into your deployment pipeline status.
  • Lots of helpful plugins that are well supported.
  • Setup on Azure was quite straight forward.
  • It does require setup unlike other SaaS products like CircleCI which just require an account.
  • Lots of plugins is also a disadvantage as you need to install quite a few and installation errors are not always easy to decipher.
  • The UI could use better search options, especially through the logs.
If you haven't used Jenkins before and have a relatively simple and straightforward deployment setup I would not use my resources on Jenkins and go for a simpler, more SaaS-based solution. If you expect to have a lot of security demands and need control of your CI/CD pipeline I would use Jenkins for the get-go.
Read Sagiv Frankel's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
Jenkins is the tool we use for building our code, running our test cases and also for few of the inhouse datacenter deployments.

Apart from the regular CICD, we also use it for many of our other automation tasks, for example automating regular operational tasks like disk cleanup, log rotation etc.
  • Jenkins has plugins for achieving anything and everything.
  • Jenkins is very flexible and has gone beyond just the CI capabilities.
  • Very active development and frequent releases with new features and bug fixes.
  • Very good authentication/authorization features with fine-grained access control.
  • Sometimes installing the wrong plugins ends up with Jenkins in a non-startable state.
  • When there is a huge number of builds, loading the Jenkins UI takes minutes. Sometimes times out as well.
  • Lacking user level minute audit logging. It's difficult to find out which users installed/upgraded plugins.
  • There were cases where jobs were in a hung state and could not be aborted as well. Jenkins restart was the only solution.
Jenkins is a good tool to automate anything and everything. It has plugins to integrate with any other systems.
Earlier Jenkins was more like a CI tool. But now it has evolved to cater for continuous delivery and deployment as well.

Jenkins can be used to download code from a source code versioning system, build code, run tests, upload to artifact repositories and finally deploy to the required environments via shell scripts, Chef, Ansible etc.

Apart from this, Jenkins can be used to run any kind of automation required, for example, operations scheduled activities like cleaning up disk space, rotating logs etc.
Read this authenticated review
No photo available
July 05, 2018

Jenkins at a glance

Score 8 out of 10
Vetted Review
Verified User
Review Source
Jenkins is used for automating the build process of testing, deployment, and release. It makes continuous deployment faster and an automated process. It is used across the organization.
  • Automated deployments. Developers manage their own code throughout the SDLC
  • Jenkins workers can be easily scaled making multiple projects use the same Jenkins for deployment
  • Easy setup of the environment using docker and Kubernetes
  • Jenkins UI needs to be changed. It doesn’t utilize the modern web technologies
  • Parallel builds should be displayed separately.
  • Containers within containers for golang creates problems in dependency management
Jenkins is well suited for a continuous integration and continuous deployment process. Jenkins file creates deployment automated as a code through docker.
Read this authenticated review
Kevin Van Heusen profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
Jenkins is currently used to build and deploy our Amazon infrastructure. We practice the principles of infrastructure as code, meaning our infrastructure config and setup is checked into a revision control system and built via Chef and other scripts. Jenkins manages building that automatically or on demand and ensures that everything that is checked in is working properly.
  • Configurability - Jenkins supports all sorts of options for different build types (Microsoft, Unix, etc.).
  • Performance - The Jenkins user interface responds pretty well and can handle a number of projects.
  • Plugins - Generally if you have a third party system to integrate with, Jenkins generally has a plugin for it.
  • User Interface - The UI feels a bit dated and can be hard to use at times.
  • Error messaging could be friendlier - sometimes it can be hard to decipher what went wrong.
  • Configuration of roles could be easier. It would be nice if it was easier to give access to certain users for certain build options/projects/etc.
Jenkins is very well suited for someone in need of a Continuous Integration and Continuous Delivery solution. It does well for people with Unix/Mac based projects, it does handle Microsoft builds fine as well, however the setup of it and configuration may feel a bit more complicated for those coming from a Microsoft background.
Read Kevin Van Heusen's full review
Neale Foulds profile photo
April 02, 2018

Jenkins CI/CD

Score 10 out of 10
Vetted Review
Verified User
Review Source
We primarily use Jenkins as part of our build infrastructure for compile and build, typically executing mavens builds but also ant scripts for more complex tasks and workflows
  • Is an excellent automation container
  • Is excellent at integration with many other tools and services
  • Is superbly well supported in the dev community with over 1k plugins
  • Is very easy to recruit for, having high market penetration and lots of candidates with experience
  • Has a number of security models to suit any enterprise or small user
  • Is very scalable both horizontally and vertically
  • History retention is an area that should improve
  • Trend analysis should be better supported in the core product
  • Dashboards need to be better provisioned in the core product
It is well suited to build, continuous integration and continuous deployment. A less common use case, the tool is also good for scheduling, offline tasks, environment maintenance such as log rotation etc.
Read Neale Foulds's full review
Aiman Najjar profile photo
January 19, 2018

Unparalleled Flexibility

Score 8 out of 10
Vetted Review
Verified User
Review Source
Jenkins is an extremely powerful continuous integration/continuous delivery tool. It can be used to automate a very diverse set of operations - including, but also well beyond, application deployments. This is thanks to amazing flexibility and the impressive number of available plugins.

In the traditional sense, Jenkins easily addresses the following problems:
  • Build and release automation
  • Test automation with result report generation
  • Test coverage reports
  • Version control polling
  • Status notifications
  • Conditional, concurrent and branched pipelines
  • Master-slave architecture
  • Credentials storage
  • Really, any custom scheduled or event-driven (primarily via version control events) workloads - of course don't go crazy with that, you don't want to schedule data science jobs on Jenkins for example. Key word is "operations".

Thanks to its large community and amount of available plugins, you can easily:

  • Integrate with Slack to push notifications, also true for many other chat services
  • Integrate with GitHub, GitLab, Bitbucket via hooks (as opposed to polling)
  • Create and restore backups
  • Integrate with external authentication providers (e.g. OAuth)
  • Define your pipelines as code


  • Large and diverse selection of plugins
  • Build and release automation
  • Operations automation
  • Does not encourage modular and repeatable design patterns: while Pipeline plugin (pipeline as code) partially solves the problem but it's not quite there yet. You cannot encapsulate your entire pipelines in self-contained, reusable and deployable code.
  • Jenkins hasn't caught up in treating containers as first-class citizen. Workloads run directly atop the Jenkins node. This means potential security issues and lacking the ability to constraint resources allocated to workloads.
  • It's very plugins-driven. Although the quantity and diversity of available plugins is amazing; but the plugins architecture makes it easy to bloat your Jenkins node with plugins and destabilize it over time. Plugins are installed globally (with ability to enable/disable at job-level).
Even though Jenkins was designed primarily for CI/CD, I wouldn't say that CI/CD is its greatest strengths at this time and age. Many modern CI/CD tools have emerged recently which specifically target CI/CD problems in lean, code-driven and containerized approach.

Ironically, that makes Jenkins ahead of those CI/CD-focused tools in solving non-traditional problems. I would still think of Jenkins as first choice for following use cases:
  • Automating Standard Operating Procedures - e.g. when you want to give your T1 support team a UI with single-click button to perform a routine SOP.
  • Scheduled test and validations that are not tied to releases - e.g. I've used Jenkins to automate data consistency tests across two layers of data stores and generate a nice HTML report of detected discrepancies, and also notify when any are found!
  • Workloads that require generating custom reports
  • Any other custom operations automation

Read Aiman Najjar's full review
Deva Veluchamy profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
Jenkins is one of the best open source Continuous Integration and Continuous Deployment tools. It is used in most of the projects in our company where we need a CI/CD pipeline. In the aspect of test automation, it is most helpful for the continuous executions whenever there is a new build.
  • Provides good CI/CD pipeline
  • Not a platform dependent, available for various operating system
  • Huge list of plugins to integrate with many products
  • Easily configurable and good documentation
  • Results metrics could be improved to get good reports.
  • Environment management can be improved, which is not quite straightforward.
  • Initial setup and configuration will be challenging.
Jenkins suite is well where we need to implement continuous integration and continuous deployment is needed. In test automation, it is possible to trigger executions automatically whenever we have new build generated or automation script changes committed. This is helpful to get quicker feedback about product quality. As plugins are available for leading test automation tools, it is also possible to easily integrate.
Read Deva Veluchamy's full review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
Jenkins is used across our entire organization. For our dev shop, it mains our build cycle by completing builds of code and handling deployment of code. In addition, we even utilize it to roll out database schema changes. If this wasn't enough, we also utilize Jenkins to generate content based off of markup. Jenkins has allowed us to meet the needs of our dev department of continuous integration while allowing customers to put out content in a timely manner.
  • Jenkins will allow you to setup continuous integration quickly for your development lifecycle. In addition to setting up your code to compile and perform unit testing, Jenkins can handle deploying the code to the needed servers.
  • Jenkins will allow you to set up processes that you wouldn't even expect to need - in our case we used it to manage our database schema by utilizing the ability to run scripts to run liquibase updates.
  • Jenkins has so many plugins, you can even integrate your deployments to update the associated task when it is ready for QA. In our case, we utilized plugins to integrate with JIRA and to notify us in our team chat that a build was ready for testing.
  • When setting up plugins, it can be tricky when you run into errors as sometimes the errors are not explanatory.
  • Jenkins requires plugins for most tasks, it would be nice to see things that are needed for most installations to be out of the box. This would tie them into the product more nicely and hopefully make those plugins easier to use.
  • Lucky for us, we run a fairly monolithic codebase which makes unit testing easier to set up. However, research shows that setting up this type of testing for micro-services with Jenkins is problematic as you cannot test multiple services at once.
Jenkins is wonderful for technically proficient users to setup continuous integration quickly. In addition, if you have processes that are currently only available via command-line utilities - you can setup Jenkins jobs to run these and this now makes those jobs accessible for users who cannot or will not use command-line. In addition, the easy to use interface allows more than the tech team to utilize jobs after they are set up allowing you to spread the workload for manually triggered jobs.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
My organization has deployed Jenkins as the main continuous integration tool for their projects which is responsible for automating all the unit tests, integration tests, end-to-end tests and also the process of releasing the final products as configured.
  • Jenkins creates a comprehensive platform to automate the project builds.
  • Jenkins can be configured to build the projects as periodically (nightly builds) or in the event of subversion commitment.
  • Jenkins provides a user-friendly portal to do the configurations you need.
  • Jenkins can improve their product by integrating agile frameworks for the platform directly.
  • They can think further on Jenkins to improve the security as such issues were claimed in the recent past.
  • Jenkins UIs are sometimes slow responsively.
As an open-source product, Jenkins can be recommended for any company who needs continuous integration/delivery for their projects. However, Jenkins offers the extended functionalities through their plug-ins which seems good in most cases but sometimes, this may lead to having unwanted functionalities and security issues in the platform in the case of using of multiple plug-ins for doing a specific task.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
Currently Jenkins is being used across the IT team in our organization. It simply does the hard job of automating all the repetitive tasks, includes details in projects, inside builds, follows workflows, accesses operating systems, and alerts when it's done, or, based on decisions during tasks, what to do. This reduced a lot of work for our dev teams, but also now is helping the infrastructure team and other departments. The knowledge of Jenkins utilization replicates really fast inside our organization as at least one people inside every team learned about or knows how to use it to build a simple job to automate a task, workflow or a deploy. Jenkins also allows us to monitor what's being done, helping managers and the team have an overview of how a pipeline is running. Another problem that Jenkins solved is centralizing automation. As it's controlled by a web console, it's easy to check what is being done, access logs of old jobs, view the entire console output and know exactly who and when a job was last executed. Also, you may set permissions by project, by job, or what you or your organization needs.
  • Continuous Delivery
  • Continuous Integration
  • Automation
  • Single Sign On
  • User Interface
  • Dashboards
Jenkins is well suited for continuous integration, continuous delivery, task automation, deploy automation, detailed security, audit jobs, dashboards, central console to manage, orchestration of jobs (starting a job after your current job was finished with success, for example). But if you wish to continue running things manually, or enjoy it, this is definitively not a tool for you.
Read this authenticated review

About Jenkins

Jenkins is an open source continuous integration tool.
Categories:  Build Automation

Jenkins Integrations

Jenkins Technical Details

Operating Systems: Unspecified
Mobile Application:No