Skip to main content



What is Jenkins?

Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery…

Read more
Recent Reviews

TrustRadius Insights

Jenkins has been widely used for various use cases, making it the go-to choice for building, testing, and deploying projects. Its …
Continue reading
Read all reviews


Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation


View all pricing

What is Jenkins?

Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

32 people also want pricing

Alternatives Pricing

What is CircleCI?

CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…

What is Buildkite?

Buildkite is a CI and build automation tool that combines the power of the user's own build infrastructure with the convenience of a managed, centralized web UI.

Return to navigation

Product Demos

CI/CD Pipeline Using Jenkins | Continuous Integration & Continuous Deployment | DevOps | Simplilearn


Jenkins in Five Minutes


12 Soft Pastel Techniques for Every Artist / PLUS Painting Demo


DWTS - Troupe waltz demo w/opera singer Katherine Jenkins


How to run Ansible playbook from Jenkins pipeline job | Ansible Jenkins Integration| DevOps Tutorial


08 - Jenkins pipeline integration with git & maven | Jenkins Pipeline Tutorial

Return to navigation

Product Details

What is Jenkins?

Jenkins Video

What is Jenkins?

Jenkins Integrations

Jenkins Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.

Reviewers rate Performance highest, with a score of 8.9.

The most common users of Jenkins are from Enterprises (1,001+ employees).
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings


Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Jenkins has been widely used for various use cases, making it the go-to choice for building, testing, and deploying projects. Its compatibility with GitHub has made it a popular option among users. One key use case is automating the build process, which has significantly reduced the level of effort required by engineers. By coordinating internal infrastructure teams with external development teams, Jenkins ensures consistent and automated deployments. It also proves invaluable in quickly bringing servers back up after power outages by running scripts. Another important use case is automating builds for different projects, reducing compilation time and allowing for sharing build scripts across repositories.

Jenkins plays a crucial role in code testing, documentation, code analysis, integration testing, and user acceptance testing. It ensures a smooth release process, performs feature builds, and handles deployments effectively. The software's strength lies in its ability to support continuous integration and automation. With its support for various technologies and platforms, Jenkins makes the development flow fluid. Additionally, it can easily scale out across multiple machines and support simultaneous builds, tests, and deployments.

Jenkins is commonly utilized as an R&D build and deploy pipeline, facilitating end-to-end and unit testing. It also finds extensive use in building and deploying AEM applications with separate instances for each project. Whether running API tests automatically or conducting automated UI tests, Jenkins helps streamline the quality assurance process. It is frequently employed to control builds for different environments such as dev, QA, and prod.

Organizations leverage Jenkins to automate CD/CI jobs across various applications, enabling automatic testing and deployment. It proves instrumental in building, testing, and deploying micro-service architectures at scale. Moreover, Jenkins generates reports and notifications throughout the process to improve efficiency and visibility.

With its flexibility in managing build servers and supporting cross-platform testing and automation tasks, Jenkins becomes an essential tool for code tests, configuration management, and test routine execution. It automates the CI/CD process by receiving commit events, building, testing, and deploying code seamlessly. Many organizations rely on Jenkins to deploy client projects in development and production environments, streamlining the deployment process.

Jenkins integrates with other tools and platforms such as SVN, GitHub, and Docker, providing a seamless workflow and enhancing productivity. It serves as a versioning system, storing build versions and facilitating code management. Furthermore, Jenkins assists in deploying applications to different environments while also aiding in server backups and restoration. The extensive range of plugins offered by Jenkins allows users to customize and enhance their experience with the software.

Overall, Jenkins has proven to be a straightforward and reliable tool for continuous integration once it is set up. It offers users the ability to test their code in a cloud environment, mimicking a production setting and facilitating faster deployment. With its robust features, Jenkins also serves as a versioning system, storing build versions and facilitating effective code management.

One of the key advantages of Jenkins is its seamless integration with other tools and platforms. It seamlessly integrates with SVN, GitHub, Docker, and more, allowing for enhanced workflow efficiency. This integration enables users to leverage their existing tools and workflows while incorporating Jenkins into their development process.

Furthermore, Jenkins is widely utilized for deploying applications to different environments such as development and production. Its ability to handle server backups and restoration is invaluable for maintaining data integrity and disaster recovery.

Additionally, Jenkins provides extensive reporting capabilities throughout the build and deployment process. This improves efficiency by providing visibility into each step of the pipeline, allowing teams to identify and resolve issues promptly.

The wide range of plugins offered by Jenkins enhances its functionality and allows users to customize their experience based on specific project requirements. This flexibility makes it a versatile tool that can be tailored to meet the needs of different teams and organizations.

In conclusion, Jenkins has established itself as a trusted solution for building, testing, and deploying projects across various industries. Its compatibility with popular platforms like GitHub combined with its automation capabilities make it an ideal choice for any organization looking to streamline their development process. By automating tasks, reducing effort, improving collaboration between teams, and providing crucial reporting features, Jenkins empowers teams to deliver high-quality software efficiently.

Automated Build Process: Many users have found the automated build process in Jenkins to be great, emphasizing its efficiency and reliability. They appreciate the seamless automation of tasks, from compiling code to deploying applications, without human intervention. The ability to run code against any testing suite and automatically rollback faulty programs has been particularly valued by reviewers.

Supportive Community: Jenkins has garnered praise for its extremely supportive community that readily offers assistance and troubleshooting guidance. Reviewers have specifically mentioned how valuable it is to have a strong network of experienced users who are willing to share their knowledge and help others overcome challenges.

Connectivity with Multiple Clouds: Users highly value Jenkins' support for connectivity with multiple clouds, including Azure, AWS, GCP, OCI, and more. This feature enables them to deploy applications across different platforms seamlessly. Several reviewers have expressed their satisfaction with this flexibility as it allows them to leverage various cloud services based on their specific needs.

Confusing and Outdated User Interface: Several users have criticized Jenkins for its confusing, outdated, and visually unappealing user interface. They feel that the interface could be improved with a more modern design using the latest UI technologies.

Difficult Setup Process: The setup process of Jenkins has been described as difficult by some users, particularly when it comes to configuring it to successfully run software builds and managing dependencies. This complexity can be frustrating for new users who are trying to get started with Jenkins.

Frequent Logouts: Users have experienced frequent logouts while using Jenkins, which can be irritating. This interruption in their workflow hinders their productivity and adds unnecessary frustration.

Users frequently recommend Jenkins as a helpful tool for new users, as it aids in avoiding issues. They believe it is an amazing tool for CI/CD and suggest using it in conjunction with GitHub. Many users argue that all projects should implement Jenkins and recommend using it for managing releases. Furthermore, they highlight Jenkins as a powerful tool for achieving continuous integration and strongly recommend its use, given its proven track record. Overall, Jenkins receives positive endorsements from users due to its user-friendliness and effectiveness in streamlining development processes.

Attribute Ratings


(1-25 of 69)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
We use Jenkins in multiple ways. As part of the QA team, we use Jenkins to run all of our API tests automatically and report back to us. We have some tests that we have special emails for every time they run. We also use it to run our automated UI tests. On the dev side, we use Jenkins to control our builds; we have pipelines in place for our dev environments, qa environments, and formal and prod environments. We then can control which environments get built. We also have pipelines in place for after-power outages so that we can quickly and effectively bring all our servers back up, which run scripts to do so.
  • Scheduling jobs is quick and easy.
  • Lots of plugins and integrations.
  • Quickly add jobs with very similar run settings.
  • The UI could be slightly better, it feels kind of like the 90s, but it works well.
  • An easier way to filter jobs other than views on the dashboard.
  • An easier way to read the console logs when tests do fail.
In our company Jenkins is very well suited; it integrates with all our tools, and it is easy to use and manage. We run all our backend API tests and our front-end UI automated tests with the help of Jenkins. The script builds work wonders for us in bringing back up critical infrastructure after an outage.
Score 10 out of 10
Vetted Review
Verified User
We use Jenkins in our continuous integration pipelines. With Jenkins, we build and test our microservices. We also make extensible use of the plugin capability (we also develop and maintain internal plugins) to cover complex build/testing scenarios.
  • Extensive documentation
  • Big community and popularity
  • Easy to extend and customize
  • Improve configuration portability
  • Improve scalability
  • Increase interoperability with containers
  • Introduce ways to update common dependencies automatically (eg Docker)
Jenkins' strengths are:
  • Scripting: Using Groovy we can extend the plugins' behavior and customize the way we build our projects. If you have complex pipelines and tricky build scenarios, please consider the use of Jenkins.
  • Maturity: Nowadays we have powerful CI alternatives, but Jenkins is a tool used for many companies and has an active community so it's easy to find documentation related to almost any setup, also there are plenty of people with knowledge about it.
Some areas where Jenkins needs improvement are:
  • Updating: Jenkins needs to introduce/facilitate ways to update external dependencies.
  • Scalability: For some workloads, Jenkins still has issues with performance.
Score 10 out of 10
Vetted Review
Verified User
We used Jenkins to implement deployment automation through CI/CD pipeline. Deployment has been easy now. We were building and deploying our applications manually into DEV, test and PRD environments. It was time consuming and it involved repetitive tasks, we used the jenkins to remove all these manual tasks.
  • Automated build package
  • Automated deployment
  • Automated job run
  • Performance improvement
  • Handling plugins is difficult
  • UI is outdated
Its easy to configure for simple pipeline deployment. Saves lot of time and manual efforts fir build and deployment.
May 22, 2023

Jenkins - review.

Muhammad Arsalan Niazi | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We utilized Jenkins to enable Continuous Integration and Deployment on 100s of our microservices. Deployed the Modular Pipelines architecture on Jenkins to enable seamless CI/CD between services utilizing different frameworks. So the thing is our pipelines facilitate the CI process from checking out code to building the artifact and then deploying it on Kubernetes.
  • Used Jenkins as CI/CD tool.
  • Extremely supportive community.
  • Support connectivity with multiple clouds so the deployments over Azure, AWS, GCP, OCI and etc are supported.
  • Trigger builds and deployments on Linux or Windows agents without issue.
  • Support multiple version control tools.
  • High memory utilization.
  • Troubleshooting at times is hard as some plugins have bad error handling.
  • Master/Agent connection must be more robust.
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Score 9 out of 10
Vetted Review
Verified User
My company uses Jenkins for building, testing, and deploying our projects. Since you can have all these plugins and works with GitHub, Jenkins seems to be the obvious choice. Jenkins also offers code quality as it has plugins to check the code. This helps us as we know if the Jenkins run fails or goes below the score quality, then we can catch major problems before they are deployed.
  • Building
  • Code quality.
  • Deployments
  • Testing
  • Documentation
  • Logging
Since I have worked with Jenkins, it has been reliable 9 out of 10 times. Considering you can build a docker file, test your code, have a Sonar plugin for quality control, and then deploy the docker image all in one, this makes Jenkins very convenient to use. There have been times when Jenkins does not run. I am unsure if it is due to how many people are using the instance. It doesn't give a great description of why, which is the only time I have had negative issues with Jenkins.
Damon Darling | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
The workflow begins with developers submitting pull requests containing their code changes and documentation. Jenkins automatically triggers builds, running unit tests to verify functionality and code analysis tools to assess quality and adherence to standards. Integration testing follows, ensuring seamless component interaction. User acceptance testing occurs in a dedicated environment, allowing stakeholders and users to provide feedback. Jenkins generates reports and notifications throughout the process, keeping stakeholders informed. Finally, upon review and approval, Jenkins handles the deployment to the production environment. This streamlined approach improves efficiency, consistency, and visibility, ensuring high-quality software releases.
  • Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
  • Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
  • Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
  • User Interface: The Jenkins user interface can be complex and overwhelming for new users. Improving the user experience and making it more intuitive would help streamline the onboarding process and enhance usability for both beginners and experienced users.
  • Configuration Management: Managing and configuring Jenkins can be challenging, especially when dealing with large and complex projects. Simplifying the configuration process and providing more user-friendly options for managing pipelines and jobs would be beneficial.
  • Scalability: As projects grow and the number of builds and jobs increases, Jenkins can experience performance issues and scalability challenges. Optimizing Jenkins for larger-scale deployments and providing better support for distributed builds and parallelization would help address these limitations.
In a scenario where a small software development team is working on a simple project with minimal codebase and a straightforward deployment process, Jenkins may not be well suited. The overhead and complexity of setting up and maintaining Jenkins could outweigh the benefits of such a small-scale project. Additionally, the learning curve associated with Jenkins, along with its resource-intensive nature, might not be justifiable for a team with limited resources and a shared infrastructure. Alternative lightweight CI/CD solutions that offer streamlined workflows and require minimal configuration may provide a more suitable and efficient choice for small projects with straightforward requirements, focusing on simplicity, speed, and ease of use.
Prashant Chaudhari | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
We use Jenkins for CI/CD.
  • Setting up pipelines.
  • Integration with other systems like Github/Bitbucket.
  • Single Sign-on.
  • Granular Permissions.
  • A lot of plugins for almost everything you need.
  • The interface can be better.
  • Upgrades are tricky.
  • Installation and set up are a bit tedious.
You can set up Jenkins for pretty much any kind of CI/CD requirements. It has plugins for supporting various environments and with Shell scripting options, you can customize it to your use cases very easily.
Score 8 out of 10
Vetted Review
Verified User
My team primarily uses Jenkins, an application deployment tool. We create automated jobs that test code and then deploy to servers/containers and restart the apps. We have also begun implementing several CI/CD uses where we are able to automate jobs to deploy container infrastructure code to Git and have runners automatically deploy into our environments.
  • Works with Git very well.
  • Easy to write in preferred coding language.
  • Easy to allow varied levels of access to different jobs/dirs.
  • Large selection of plugins to customize.
  • Jenkins config.yaml recovery is not smooth and takes a lot of legwork.
  • Plugins that go out of date can cause issues with upgrades.
  • Progress UI frequently lacks detailed descriptions from Jenkin's side.
One scenario we use Jenkins regularly is with a scheduled Jenkins job (akin to a cron job) that runs every morning and takes inventory of all VMs/Containers/Servers. This inventory monitors changes in average resource usage, and services that are up or down, and backs up logs for troubleshooting. This job requires no attention, and Jenkins manages it all automatically. Another scenario in which Jenkins was utilized less effectively was in an attempt to actually manage virtual machines (spin up/spin down/reallocate) in vSphere. While we eventually got it to work, Jenkins had a hard time interpreting some of the logic we provided it. Admittedly, Jenkins may have a plugin to assist with this need, we simply found it tedious and decided to go another route in the long run
Score 10 out of 10
Vetted Review
Verified User
For nearly the last decade, we have used Jenkins as an automated build tool platform. My company does a lot of in-house app development. Like many other IT shops, Jenkins is a key component of continuous integration continuous deployment (CICD) pipelines. Allows us to schedule jobs automate film processes, deployment processes, server bounces, etc. It's capable of doing a myriad of options, anything from simply pushing a shell file to run token replacement, ant or Maven scripts, automated scheduled builds, on-demand execution, and trigger-based runs. We can even use it to interface with AWS for deployments to the cloud.
  • It's fantastic at cutting down on manual steps for building and deploying ear and war files.
  • Excellent tool for scheduling deployments.
  • Trigger-based builds, such as when code is checked into a repository like GIT, are a strong suit of this tool.
  • It can sometimes be difficult to navigate, especially when you're trying to drill down into configurations that are sourced outside of your job but referenced by the job you're designing.
Any kind of app development where you need to build code on a regular basis and deploy it to static environments is an excellent use of Jenkins. Anytime developers were manually building and deploying could therefore be automated in Jenkins, design jobs for either on-demand execution, scheduled builds, and even trigger-based builds.
Score 7 out of 10
Vetted Review
Verified User
Jenkins runs our continuous delivery and deployment pipelines for multiple on-premise environments. Through the use of its plugins, we're able to extend its capabilities.
  • Stability
  • Extensible by plugins.
  • Dated UI.
  • Jenkins DSL for writing pipelines instead of YAML.
Jenkins is a great pick if the team already has experience with it, mostly because it will get the job done. There are new CI/CD tools these days for achieving the same use cases which are more integrated into e.g. SCM.
Score 9 out of 10
Vetted Review
Verified User
Our organization uses Jenkins to pull source code from our SVN repository, build it and then deploy it. This allows us to effectively manage which version of the code is deployed to a specific environment. We control access to production builds to only a few individuals within our organization while giving developers the ability to deploy code to our development and test environments.
  • Integration with TeamForge.
  • Controlling access to building jobs.
  • Proving a history of what was deployed and when.
  • Better upgrade process and documentation.
Our organization has a team of approximately 30 developers. Using Jenkins allows us to effectively manage access to who can promote which projects, and which environment they can promote them to. The detailed build history is very useful in instances where a build fails.
Eric Mintz | TrustRadius Reviewer
Score 3 out of 10
Vetted Review
Verified User
I used Jenkins to build and configure docker images and then deploy them to an AWS virtual private cloud (VPC). The Jenkins instance was responsible for automating the continuous integration and continuous deployment process (CI/CD) by receiving commit events from GitHub, extracting, building, and testing the source code, and then deploying when testing succeeds.
  • Provides at-a-glance a visual representation of the pipeline's successes and failures.
  • Executes the deployment process on the remote hosts via agents.
  • It is controllable via yml configuration files which themselves can be in version control.
  • The Jenkins application is difficult to deploy using tools like Ansible since plugin installation and configuration aren't easily scriptable.
  • Jenkins depends on plugins for even the most basic use cases, like user and role-based access control. These should be built in.
  • Jenkins yml-based configurations are only testable by editing the yml in the web GUI (which is very tedious and error-prone) or by yml files that are committed to source control (which makes it slow and inconvenient). It should instead have the option to use local yml files.
Jenkins is suitable for use cases where the initial lengthy, manual setup time can be justified and where once it's set up, little change is expected to the pipeline. Jenkins is less suitable for cases where: The Jenkins instance itself will be deployed by infrastructure-as-code (IAC) tools like Ansible Jenkins pipelines are expected to undergo substantial changes during development. There is no dedicated resource to constantly check for Jenkins plugin upgrades.
Score 6 out of 10
Vetted Review
Verified User
We use it for our continuous integration. Builds are made every time a PR is merged into a master. It works pretty slickly, and when it's working perfectly, nobody needs to really think about it. It just does its thing. Jenkins is fairly straightforward and good once it is set up.
  • Shows build progress.
  • Shows error messages.
  • Just works after being set up.
  • Hard to get going.
  • It can be hard to diagnose problems.
  • Parts of it are not well designed.
Jenkins is perfect if you want to relatively fuss-free continuous integration solution.
Score 8 out of 10
Vetted Review
Verified User
We are using Jenkins as CI/CD tool. We have implemented Jenkins in Kubernetes with master and worker pods. Worker pods are automatically provision and depletion base on when job is triggered. first step is trigger, Jenkins pipeline will be triggered when code is pushed in Github in particular branch. second step is to build a docker image and push it docker registry and third to apply/deploy in k8s.
  • Jenkins is highly customizable and can be extended with plugins to meet specific needs. There are thousands of plugins available in the Jenkins plugin repository that can be used to add new features or integrate with other tools.
  • Jenkins can be used to run automated tests as part of the build process. It can execute unit tests, integration tests, and other types of tests. Jenkins can also integrate with popular testing frameworks such as JUnit, Selenium, and TestNG.
  • Jenkins is well-known for its ability to perform continuous integration. It automates the process of building and testing software every time a developer commits a change to the source code repository. This ensures that the codebase remains stable and any issues are identified early in the development cycle.
  • Jenkins can be vulnerable to security issues due to its open-source nature and the availability of many third-party plugins. There have been instances where malicious plugins have been discovered, and these can pose a significant risk to organisations.
  • Jenkins can require a significant amount of maintenance, particularly when dealing with plugin updates and compatibility issues. Maintaining a stable and up-to-date Jenkins instance can be a challenge for organisations with limited resources.
  • Jenkins' reporting capabilities are limited, and it can be challenging to extract meaningful insights from the data that Jenkins provides.
Jenkins is well-suited for scenarios such as Continuous Integration, DevOps Automation, Agile Development, and Open-Source Software Development. It may be less appropriate for small projects, legacy systems, complex configurations, and low-resource environments. It's essential to carefully consider the specific needs of your organisation before choosing Jenkins or any other automation tool.
October 12, 2022

Jenkins makes life easy.

SHEETAL KUMAR MAURYA | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
All the client projects are deployed by using Jenkins in the development and production environment. Jenkins saves lots of time by automating the deployment process. It is easy to install and manage, so a non-Develop employee is also able to do a complete deployment of any app and project.
  • Repo cloning and build.
  • Transfer build to prod and staging servers.
  • Version Management.
  • Plugin Support.
  • Try to focus on reducing its size.
  • Required a high performance server.
  • RAM is highly utilised.
  • After build of App, Hard to setup code transfer from Jenkin server to other.
It is best suited when your deployment is widespread, and you don't have time to do this. Also, it is suitable if you have less knowledge of servers. I would not suggest Jenkins if you do not have frequent deployment. It requires at least medium size instance to run so that it will make a recurring cost.
Sayam Jain | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Jenkins is one of the important tools which we are using in our organisation. With the help of Jenkins we have set up almost each and every automation our organisation is required. From the deployment of the software to the monitoring Jenkins is helping us in a very smart way. All the development is been pushed on the testing UAT and production servers with the help of Jenkins.
  • It helps in automating your general day to day tasks.
  • Almost each and every language tool is been integrated in it.
  • Timely update are managed by its community.
  • It provides APIs which can be used in integrations.
  • Community support only.
  • Finding Actual Error from the Stack trace.
Any work that requires a regular same kind of iteration can be done or achieved by the Jenkins, from small mailing of monitoring to large part of deployments are handled with Jenkins with ease. Jenkins is somewhat tough to set up, but once you get some hands-on then you can automate almost every iterative work.
ANurag Tamrakar | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We're using Jenkins as a Continuous Integration and Continuous Deployment tool in our organization, We are deploying, administrating, and managing multiple instances of Jenkins for a large number of teams. As it supports multiple kinds of Jobs and pipelines it's well suited to all the teams across our organization. By decommissioning enterprise CI Tools we started Using Jenkins and we're saving a significant amount of money.
  • It offers multiple types of Jobs and pipelines which makes automation easier.
  • We're using Jenkins as a CI tool, We are administrating and managing it for a large number of teams.
  • Feature and functionality wise It's far better than all other enterprise CI tools.
  • We have only community support so sometimes it can be problematic to troubleshoot or fix issues.
  • Most of the plugins are developed and managed by open-source contributors so we've to rely on the mercy of collaborators or to develop our own.
  • Sometimes it's very hard to troubleshoot the issues due to improper error handling in plugins.
If you're looking for a highly customizable CI/CD tool then Jenkins is a go-to Tool! if you're looking for developing and using your own features you're in. You can develop your own plugins in Jenkins. Jenkins requires maintaining servers and building agents if you're looking for something maintenance-free then you should look for SaaS-based CI/CD tools.
Caleb Kleveter | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Jenkins is the frontline tool used by our Device Integrations team to ensure a smooth release process for each version of our app, whether that is doing a feature build for our QA team, uploading a new version for release day, or simply making sure each new PR builds and passes our test suite before merging into our main build branch.
  • Full customization with a complete library of plugins and raw shell build steps
  • Credentials handling with built-in storage
  • Custom environments with locally hosted instances
  • The UX is messy compared to other solutions
  • Jenkins doesn't have the best method of storing job configs in its related repo, unlike GitHub Actions or CircleCI
  • You can't easily set an environment variable for the rest of your job from within a build step, if at all.
Jenkins is good if you need to have a CI system so flexible that it would make a gymnast look like a block of wood. In every case that I have worked with, other solutions have been easier to use and maintain, while having all features I could ever need.
August 03, 2021


Score 8 out of 10
Vetted Review
Verified User
Jenkins is used by my team to automate the build pipeline we have for our codebase. We use it to run builds on our code base automatically on a daily basis to help maintain the functionality of the code. It also automatically runs test cases for each push of code to our repository. It allows users to test their code in the cloud instead of locally and helps mimic a production environment.
  • Jenkins is an open-source CI/CD tool with a massive community and lots of plugins and functionality.
  • We are able to use Jenkins with multiple source code repositories and with various other tools.
  • Jenkins has a very active user base and is very frequently updated to add features, security fixes, and other enhancements.
  • Open source Jenkins has little in terms of formal support so it can be problematic to troubleshoot some issues.
  • Jenkins plugins are created and supported by the community in most cases so you are at the mercy of the collaborators to maintain the code unless you want to join the effort yourself.
  • There are a few popular software suites that are not fully compatible with Jenkins in their current state.
Jenkins is well suited if you need a high customizable CI/CD tool that can be integrated with most popular tools and software. It is possible to get Jenkins to do almost anything you want or need it to if you are willing to put in the effort up front. It is a great tool for running automated tests on your codebase.
July 30, 2021


Score 9 out of 10
Vetted Review
Verified User
- Jenkins is used for orchestrating automated test, CI, CD pipelines at our organization
- It is being used by a number of departments including engineering
- It solves a big need for us which is being able to deliver software and value to customers reliably.
  • Automation
  • CI
  • CD
  • Bloated and can be made more lightweight
  • Hard to discover features and workflows
[Jenkins is a] feature rich project management product for small or large teams at an organization.
Score 8 out of 10
Vetted Review
Verified User
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.
October 17, 2019

Jenkins CI/CD

Score 8 out of 10
Vetted Review
Verified User
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.
Richard Rout | TrustRadius Reviewer
Score 2 out of 10
Vetted Review
Verified User
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.
Score 9 out of 10
Vetted Review
Verified User
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.
October 16, 2019

Excellent CI/CD tool

Score 10 out of 10
Vetted Review
Verified User
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.
Return to navigation