TrustRadius Insights
Jenkins has been widely used for various use cases, making it the go-to choice for building, testing, and deploying projects. Its …
Overview
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…
Recent Reviews
Awards
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
Pricing
N/A
Unavailable
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
Offerings
- 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.
Product Demos
CI/CD Pipeline Using Jenkins | Continuous Integration & Continuous Deployment | DevOps | Simplilearn
YouTube
Jenkins in Five Minutes
YouTube
12 Soft Pastel Techniques for Every Artist / PLUS Painting Demo
YouTube
DWTS - Troupe waltz demo w/opera singer Katherine Jenkins
YouTube
How to run Ansible playbook from Jenkins pipeline job | Ansible Jenkins Integration| DevOps Tutorial
YouTube
08 - Jenkins pipeline integration with git & maven | Jenkins Pipeline Tutorial
YouTube
Product Details
- About
- Integrations
- Tech Details
- FAQs
What is Jenkins?
Jenkins Video
What is Jenkins?
Jenkins Integrations
Jenkins Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
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).
Comparisons
Compare with
Reviews and Ratings
(442)
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!
- Business Problems Solved
- Pros
- Cons
- Recommendations
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
Reviews
(51-69 of 69)Companies can't remove reviews or game the system. Here's why
September 29, 2017
Jenkins - monkey that needs to be tamed
Jenkins is used as a default tool for continuous integration across the enterprise. We have multiple instances for different applications. The slaves are auto scaled depending on the demand for builds. Jenkins builds, deploys and tests our deliverables providing instant feedback when changes are implemented. We use a numerous number of plugins to support our choice of technologies
- Distribute builds across slave farm
- Extremely flexible e.g. pipeline jobs
- Open api which means it is easy to extend
- Integrates with other tools such as SCM or project management
- Plugins can clash with each other as they are not tested together
- Upgrades can be painful, again because of plugins
- Missing support for job templates, no useful plugins exist
August 29, 2017
Amazing CI Tool
Jenkins is used as a development only tool as a manual as well as continuous integration tool with hooks into Artifactory. We have 15 build machines supporting Windows, Mac OSX and Linus Operating Systems.
- Creating a basic build job is quick and painless.
- Jenkins integrates with source control and Artifactory extremely well.
- There are so many plugins that just about anything is possible.
- Quite a few plugins have been discontinued recently due to security flaws.
- Slaves often get disconnected for no apparent reason and have had to write our own code to check and bring them back online automatically when needed.
August 22, 2017
Jenkins - The way you want
We have been using Jenkins in different areas of organization such as in Development, Test Automation and in cases for building docker images.
- Wide range of plugin base support
- Continuous Integration
- Easy installation
- GUI - There are places were you will think the UI is giving a hard time.
- Documentation on DSL
August 22, 2017
Jenkins open source build server
We use it across all the dev org. Maintenance is pretty straight forward and there are so many plugins to choose from. We have about 20-25 build machines that are continuously running jobs. It has so many hooks for svn.
- Plays well with Linux, Windows and Mac OSX build machines
- Maintenance - upgrades are pretty simple.
- Plays well with SVN. Plus so many custom plugins.
- Support
- So many bugs
- Clients constantly keep disconnecting from master
July 21, 2017
Jenkins Review
Jenkins is being used by the whole organization.
Jenkins is being used as the orchestration layer for our Continuous Delivery Pipelines. The DSL is used to set up Pipeline-As-Code.
Jenkins is being used as the orchestration layer for our Continuous Delivery Pipelines. The DSL is used to set up Pipeline-As-Code.
- Jenkins offers flexibility to implement any customer use case.
- Jenkins has a plugin ecosystem that's helpful to avoid writing too much custom code.
- Jenkins is free.
- Jenkins has a buzzing community and great docs.
- Jenkins lends itself to containerization.
- Jenkins Pipeline-As-Code should be declarative instead of requiring users to write groovy code/script.
- Jenkins should offer a better dashboard with KPIs that customers care about.
- Jenkins should improve their UI and graphical visualization of Pipelines.
April 26, 2017
Jenkins gives you time for actual coding!
Jenkins is the only CI tool that we use for software development in our organization. It's used to build and test our projects while working in big teams and constantly making a lot of changes, that need to be harmlessly integrated into existing code.
- Easy installation
- There are a lot of plugins that can be installed on Jenkins to integrate different build and analysis tools
- Open source with great support
- UI Interface is't very intuitive
- Configuration is a bit confusing
- Errors messages are not very clear about what went wrong
April 18, 2017
Most extensible CI tool we've seen
We use Jenkins to coordinate internal infrastructure teams with external development teams to make sure deployments are done in a consistent and automated fashion. This increases security in the infrastructure as well, as we do not need to create user accounts for the developer teams in the deployment environments. We use Jenkins to deploy PHP, Ruby, and .NET applications.
- Build and deployment automation. You can build almost any code base from most standard code repositories and push the artifacts to the application servers.
- MANY MANY plugins. The Plugin community is huge, so if Jenkins doesn't do something out of the box, there is probably a plugin to do it.
- Multiple step orchestration. Any build can be created with many steps, including pre and post build. Additionally, you can tie builds together.
- User management is a bit simple, and it is hard to manage users across multiple clients with the Jenkins internal database.
- Automated deployment and configuration of Jenkins itself. The config files are hard to template out and change with each version.
- Windows Slaves. Windows Java slaves are unreliable, especially when run as a service.
April 17, 2017
Quick Jenkins review from a new Jenkins user
Jenkins is currently being used to automatically build releases when a change is detected in the code base.
- Automatically creates a build and posts to company managed Jenkins page.
- Provides ability to access several builds and clearly shows successful/unsuccessful builds with time stamps.
- Ability to tie into other tools such as instant messaging apps/programs to get up-to-date information or broadcasts of when a build has started/completed.
- Jenkins provides a 'pipeline' where a user can fine tune instructions for Jenkins to execute. This pipeline is hard to use via the browser as it cannot be resized.
We use Jenkins to build and deploy AEM (java/maven) applications. We usually stand up one instance per project so that teams do not interfere with each other. At the end of the project we destroy those instances. It is used primarily for CI to dev and qa environments, and final build package delivery. It integrates with our package management system Artifactory.
We have been able to leverage existing free plugins, and not needed to write any custom or convoluted scripts.
We have been able to leverage existing free plugins, and not needed to write any custom or convoluted scripts.
- Job chains. you can break up tasks into multiple jobs and chain them together.
- Jobs are very flexible. there are many plugins available for things like maven/ant/msbuild/s3 and if you can't find one for your particular stack, you can always drop down to scripting.
- Notifications. we've used the out-of-the-box email notifications to report on failures, and we also use the Slack integration provided by a free plugin.
- Its open source, so there are times when plugins (not the core) have issues and you either have to wait for a fix, suggest a fix, or find a work-around.
- The UI leaves a little something to be desired. It seems like it was designed by engineers. fortunately there is a plugin for styling which makes it a little better.
- Version 2 is out. At the time when I tried to migrate from 1.6 I had issues because some of the plugins I use had issues in 2.0.
March 30, 2017
The most flexible CI/CD tool
Jenkins is been use as our main CI/CD software, we have a micro-service architecture that is been build, tested, deployed through all our environments qa, staging, production and all of them at scale. We also build on jenkins our mobile applications with the same flow we build test and deploy our applications to the stores reducing human error on configurations and spotting issues before we even know about it. That allow us to reach an estate of trust with our clients.
About Jenkins we are using the new BlueOcean interface, what it is really amazing; and using Pipelines as our definition language.
About Jenkins we are using the new BlueOcean interface, what it is really amazing; and using Pipelines as our definition language.
- Integration with third part tooling, testing software and platforms
- Plugin platform, really flexible and easy to develop for
- Open source
- Scalable
- Easy to install and configure
- UI Interface
- API
- Administration
March 30, 2017
Just a user of Jenkins
Jenkins was used by the development team to automate a deployment method for the customer. As such, Jenkins was a great asset working in conjunction with Git in order to provide a certain level of CM. Jenkins provided the much-needed build process that takes the guesswork out of making sure each build was done properly.
- Automated Builds to help rule out human build fails. Indicators that also notifies if a build has failed.
- Documents changes to each file in the build as well as keeping a log of the builds over time in case you have to revert.
- Works particularly well with Git repositories as the hooks automatically can trigger a new build once it has detected any updates.
- As a new user that jumped into Jenkins, it seemed a bit more overwhelming to use at first. If there was an intuitive guide that could help out the workflow would be great.
- It took a little elbow grease to get Jenkins to cooperate with Git.
- When builds fail, I wish it would give a little bit more detail in troubleshooting what went wrong.
March 30, 2017
Good son of Hudson
Jenkins is used across our company. Release Engineering department uses it to provide numerous streams of product component and integration builds, Software Development and Quality Assurance Departments use it as an outstanding Continuous Integration tool to seamlessly install new builds into various environments and to run test automation suites with automatic reports being sent to all stakeholders.
- Delivery: Jenkins does a perfect job in hands of our Release Engineering department to provide new product builds to numerous projects in timely fashion.
- Continuous Integration: Quality Assurance team does not start working on a System Test of the new build until it passed an automated Sanity Test in a CI environment.
- Delivery (again): Development and QA teams no more spending hours looking at terminal screens while installing a new build to target environment and moreover we're now guarded from human errors in this automated process, thus saving precious time.
- With growing audience of Jenkins within our company the performance and thus usability of the Jenkins control page becoming more and more critical issue. All projects are listed in a single page without paging and it's an issue when you have many hundreds of projects listed...
- Learning curve is a little too steep: newcomers spend weeks to familiarize themselves with Jenkins. Configuring a project in Jenkins is not as intuitive as we would like it to be.
January 06, 2017
I bet on Mr Jenkins for any CI work
[It is being used to] automate deployments while verifying code quality. Several jenkins jobs were defined to cover individual deployment to environments. Jenkins' pipeline makes the process more user-friendly. Jenkins supported several different software technologies from node to Java. We frequently utilise the wide variety of hooks jenkins can handle, and automatically trigger a build once the source code has changed.
- jenkins pipeline: useful to visualise the dependent job hierarchy and easy to start/stop each step manually
- Source code management (SCM): supports different types of repositories from SVN to Git and you can set different triggers after each code change.
- Plugins: jenkins can work well with lots of plugins, for instance it can render test results or run scheduled scripts seamlessly. Artifacts can be easily deployed with docker.
- UI might need a bit of improvement. I can point to material design, it' sso easy to visualise on a smart phone as well.
- Too much configuration on one page, I suggest separating out the config sections in a cleaner manner.
December 05, 2016
Jenkins is the standard for onsite build-servers
It's used in parallel with Bamboo. The iOS developers use Jenkins to do their builds. For Android, our official CI builds are done on Bamboo, but we also use Jenkins for build testing non-feature branches and for integration testing with emulators so we don't tie up the main Bamboo server which is also used for backend builds. Jenkins being able to run everywhere with lots of third party plugins is why I've always used it for cross-platform projects. Because of the huge userbase, just about every use case is covered. Pipeline has also made it a lot closer to the ease of use of CircleCI in that project build config files can be shared between projects much more easily than the old Jenkins project .xml files.
- Cross platform
- Lots of third party plugins
- Lots of examples (although Pipeline examples are little bare currently)
- The ugly UI is something that should be addressed but the Blue UI project (in Beta) looks really good.
- There should be a better way to handle redundancy/failover with the main server (Google reported this in their study as well).
- Log file should be shipped off to another server so they don't become a bottleneck (also mentioned by Google).
December 05, 2016
Jenkins is a good and practical CI tool.
I am using Jenkins for CI purposes. Jenkins especially helps me to manage the automation test in different levels: UI(functionality)/API/performance/security tests etc. It is a good framework that is integrated with other automation frameworks very well. And it has a variety of nice plugins. It provided a centralized management platform to manage all the automation testing frameworks we have. And you can also use the cron job to schedule the build running periodically to perform some performance tests.
- Good integration with lots of other open source frameworks.
- Centralized control and an easy to make build process.
- A wide variety of plugins to use.
- Jenkins' TestLink plugin result does not take .xml format result. So I have to run a script to transform .xml to .tap it is good for Jenkins to accept .xml directly.
- It would be good for Jenkins to have more graphic features that can show better analysis/test results.
- Better and more flexible project structure management.
August 25, 2016
Jenkins - Save money, time, and sanity.
Jenkins is used extensively in our engineering department. It's used to automate builds for Go, NodeJS, .NET, iOS, and Android projects. It greatly reduces the amount of time needed to compile updates, and allows us to share build scripts across repositories for setting up new jobs quickly.
- Jenkins abstracts the build/compile process, so that a local development machine doesn't need to constantly be updated or contain all of the libraries/packages required for more extensive builds.
- Jenkins allows extremely customized and parameterized builds, allowing non-technical coworkers to initiate builds and set their own parameters.
- Jenkins has a large collection of plugins that can retrieve and send build data/artifacts to/from various services, and can also hook into many popular apps like Slack and Hipchat.
- The user interface of Jenkins (2.0 and prior) still leaves a bit to be desired. Many of the options and configurations options are not where you would expect when first starting to learn Jenkins.
- Jenkins tends to require a bit more overhead than I would like in terms of RAM and dependencies.
- Some Jenkins plugins can break Jenkins in unexpected ways, without Jenkins gracefully handling errors. This is one area that could be greatly improved, with minimal effort.
August 19, 2016
Free, Simple and Powerful tool
Score 8 out of 10
Vetted Review
Verified User
Our company is using Jenkins to integrate with the code on Github; build the versions, run the complete suite of tests, and deploy to staging/production once everything is perfect.
- Ease of use of the web-interface
- Safe, secure and easy to access
- Most of the plugins work very well and can make our job easier
- It might be confusing sometimes on how to use and configure and set up the parameters
- Besides that Jenkins does everything we need at the time
June 17, 2016
Jenkins, Master of CI/CD
Score 9 out of 10
Vetted Review
Verified User
Most of the teams within the organization will roll their own Jenkins CI server to handle all build automation and CI/CD (continuous integration / continuous delivery) tasks. It allows for automation for building code, deploying applications and much more.
- Jenkins is open source and there is a great community behind it, which drives rapid development for new plugins and upgrades to the software itself.
- Jenkins allows for a great deal of customization to enable automation for any number of different workflows or development tasks.
- It is simple to install and configure for even beginner developers!
- Unfortunately, Jenkins does not have integration with all major software services. This is because it is open source and the community itself will create and publish various plugins to allow Jenkins to interface with these other services, but this means that for a specific service either we wait for the plugin to be available or we must develop our own.
- Jenkins can be used on various operating systems, although it is not simple to use or configure a heterogenous Jenkins solution (where master node and/or worker nodes have different OSs).
March 29, 2016
Jenkins is a good tool to begin an automation
I use Jenkins for a continuous integration during software development. Jenkins runs builds, tests, code quality tools. Jenkins is configured to run nightly builds automatically and run tests after each change in products. It allows us to react on troubles as fast as possible.
- Open source solution
- Flexible configuration
- A lot of plugins available
- Poor user interface