TrustRadius
Jenkins is an open source continuous integration tool.https://media.trustradius.com/product-logos/a9/F3/EHQMKIKITL3V.JPEGJenkins: The CTCI tool we've all been waiting forWe 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.,9,Has cut our deployment time drastically by incorporating automatic integration and QA testing into our workflow. Has the ability to deploy our staged code automatically once green-lit by the QA team and the software devs.,TeamCity and Travis CI,Ansible, Amazon Relational Database Service, Atom,9Simple but powerful opensource CICD toolWe 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,9,Do not have the backup or baseline for jobs scripts, accident delete jobs could not recover Pipeline only support Groovy Poor support for Docker,CircleCI,Apache Maven, SonarQube, Selenium,9An amazing tool, but far from being perfect (unfortunately)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.,9,We deliver software in a more reliable way. We perform tests which many times are requirements on the security processes. Performing all those tasks in an automated way, we are saving engineers time.,Puppet Enterprise (formerly Puppet Data Center Automation), HashiCorp Vault, Terraform, Zabbix, Docker, Kubernetes,7Jenkins: The defacto standard build toolJenkins 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.,10,Jenkins has reduced our time to market since we can integrate various deployments and test suites directly into the build Jenkins has reduced the training time required for our new engineers. Since this is the defacto build tool, most of our new hires already understand how to use it. Jenkins is also a free tool which provides these benefits without costing the company, although there are companies that provide support.,Microsoft Azure,FF4J (Feature Flipping for Java), Togglz, Ansible,10Let your workforce interact by keeping them on same page!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.,8,We mostly rely on freelancers all over the world which understand our problem statement and start to work on immediately because of Jenkins. This keeps the production safe and lets the work to carry on in another environment. Integration to GitHub helped a lot to sync our older releases of the projects. Better updates were given to the customers. The "GitHub issues" plugin is a savior for updates and patches. Most of our Ubuntu servers were ready to cope up with the technology rather than the windows systems. Thus we migrated to Ubuntu systems all over the workforce. Easy installation on Ubuntu helped in delivering the release at the right time.,Bitbucket, Codacy,9Jenkins is quick to learn and quick to implementMultiple 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.,8,It's Open-source, so there's little to no cost overhead for deploying and updating Jenkins. It's well known in the industry, so many employees are already familiar with it. Multi-platform support means we don't have to rely upon Windows OS (and associated licensing) to use Jenkins.,Chef and Puppet Pipelines (formerly Distelli),GitHub,9Jenkins - Best Open-Source Continuous Integration Software on the marketThe 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.,10,Time - No longer need to manually run deploys, test scripts, etc. since Jenkins will do it automatically for you. Resources (People) - Automating tasks requires less things needing to be done, thus not requiring as many developers Code Quality - Because of continuous integration and automation capabilities, we can put quality checks into the workflow and run tests to make sure things are working and don't break (without needing to do any extra work),CircleCI and Ansible,CircleCI, Datadog, MySQL, LastPass, Okta, Concur Expense, Concur Travel and Expense, GitHub, BitbucketJenkins as my Continuous Integration tool of choiceThis 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.,7,Has streamlined the build, release and deployment schedules with the automation it provides Very easy to run automated tests and promote code to higher environments. Scripting support helps to customize as per the organization's needs.,TeamCity and Bamboo,Puppet Enterprise (formerly Puppet Data Center Automation), Docker, Mule ESBJenkins - when you want a dedicated, non SaaS CI/CDJenkins 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.,8,Having a CI/CD pipeline, in general, helps you push new features faster and more reliably. In the short term - a large setup cost. Long-term - no cost for SaaS products.,CircleCI,CircleCI, GitHub, Trello, NanoboxJenkins provides solid support for Continuous Integration and Continuous DeliveryJenkins 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.,8,Streamlined building our server infrastructure, which gave us more time for other development efforts. Helped improve code quality - we were able to verify that the code was compiling properly with each check-in. Made deployments more bullet proof - with a standard flow for deploying our code/infrastructure, it made less room for human error.,TeamCity,TeamCity, GitHub, New Relic APM, SlackJenkins CI/CDWe 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,10,Deployment automation is the biggest gain. You can plug anything into anything using Jenkins as the UI Simplifying complex tasks via UI Capturing complexity and removing/reducing key man dependencies,Bamboo,Selenium, XL Deploy, XL ReleaseUnparalleled FlexibilityJenkins 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 automationTest automation with result report generationTest coverage reportsVersion control pollingStatus notificationsConditional, concurrent and branched pipelinesMaster-slave architectureCredentials 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 servicesIntegrate with GitHub, GitLab, Bitbucket via hooks (as opposed to polling)Create and restore backupsIntegrate 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).,8,Jenkins is a great investment if used for heavily customized workloads. For traditional CI/CD problem, the ROI will decrease as Jenkins in its current design does not encourage modular and reusable patterns,Concourse, Drone.io and CircleCI,KubernetesAutomate anything and everything with SpinnakerJenkins 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.,10,Its a great ROI. Jenkins helps in automating most of the stuff. The way Jenkins handles the scale is quite impressive. Have one master and multiple slaves of different OS types help achieve any kind of automations. We are able to achieve CICD for many applications with just one master slave Jenkins setup. The Jenkins team is very much updated with current trend technology of cloud (AWS, GC etc. ) and also supports container technologies (Docker and orchestrating it using Kubernetes ); because of this, there is no need to think of another tool for any new technologies. And enterprises can use Jenkins for long-term stability with full trust.,TeamCity and CircleCI,GitHub, Chef, Spinnaker, Docker, KubernetesJenkins turns time-consuming tasks into automated successesJenkins 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.,9,Jenkins allowed us to roll out a critical piece of our product which is a home-grown content build system. When changes are checked-in, Jenkins monitors these changes and allows content to be ready to push out when ready to go. This has allowed the CMS system to be sold to customers which offered a positive effect on ROI. The only negative impact is that some processes can be quite technical to set up - leaving this task to only be completed by either IT or the development team.,,Trello, FileMaker ProQuick review of JenkinsMy 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.,8,Jenkins provides a continuous overlook on a project's health which impacts the ROI positively. Sometimes Jenkins claims build issues due to various reasons. So taking time to resolve them may it cause to block the release process and which also affects the ROI negatively. Jenkins is open-source and it is freely available for anyone to use. Hence it impacts the ROI positively.,TeamCity,JIRA Software, Atlassian Confluence, Apache SubversionAutomate your environment with JenkinsCurrently 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,10,Speed up time from the deploy to production Reduces the errors Tracks what was done,Microsoft Office 365, Google Drive, OneDriveJenkins at a glanceJenkins 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,8,Faster deployment makes business respond to market more easily No need for a separate release management team Jenkinsfile make release deployment automated as a code,Travis CI,Google Compute Engine, Docker, KubernetesJenkins ReviewIt is being used by mostly the technology department. It allows us to run jobs between engineers and non-engineers. It increases productivity by automating processes.,Automated scheduled jobs,I think the UI is not the greatest.,8,It has saved us time and money by not having to manual run jobs It produces fewer bugs in our software by running automated tests,,Slack, JIRA Service Desk, JIRA Software, Atlassian Confluence, Google Drive, SeleniumThe venerable open source build tool trusted by companies large and smallI used Jenkins to manage both development and release builds of software at my two previous roles (IBM and Red Hat.) In both cases, each department had its own instances, so that plugins could be customized and managed on a per-team, per-product basis. It enables teams to manage a fleet of build servers (slaves in Jenkins parlance) that can build source code and run tests in an automated fashion, across platforms - this enables cross-platform software to be tested against various versions of Windows and Linux, for example. It can also be used for simple automation tasks, though other tools like Ansible are better suited for those tasks.,Minimal but extensible and flexible: Out of the box, Jenkins provides rudimentary capabilities to manage a host system with a framework for running build tasks and installing tools. There are many extension points available for plugins, and so a rich ecosystem of plugins is available. Many version control systems are supported, and integrations with other tools through plugins is excellent. Cross-platform: Supports many platforms and architectures quite easily, thanks to its implementation in Java Design focus: With Blue Ocean, you can get a nice-looking web interface for free Rich ecosystem: As Jenkins has been around for quite some time, there is a rich ecosystem of blogs, tutorials, guides, and documentation available for performing most of the day-to-day tasks you would need. There are also various vendors like CloudBees that offer hosted services. Ease of deployment: Jenkins can be deployed quite easily as a standalone JAR file. There are also system packages available for many Linux operating systems, such as Debian.,Difficult to manage build configurations: builds are generally configured through the user interface, which is easier to modify (especially for casual users rather than dedicated release engineers), but this results in changes that can be difficult to track, especially if multiple people have write access to the system. Some teams manage this by restricting people that can modify builds, but this creates a bottleneck. Ideally, the system would provide a good audit trail and change history, allowing changes to be tracked and reverted easily. Competing offerings get around this by version-controlling their configuration (e.g. Travis CI, Drone, AppVeyor) but this results in a slightly higher learning curve. Quality of plugins varies widely: plugins are in various states of maintenance, and some are woefully incomplete and no longer updated. It can be difficult to know whether a plugin is well-written or not, or even actively maintained. Builds are often not easily reproducible: By default, builds are run on the slave systems, which can retain state between runs that cause difficult-to-debug failures. It's possible to get around this by using VM snapshots and periodically reverting to clean systems, or by using the Docker plugin to run builds inside ephemeral containers. Plugins are globally scoped: Because plugin versions and the Jenkins version are per-installation, companies with multiple teams typically run multiple instances of Jenkins. This leads to a maintenance nightmare and a lot of duplicated effort across teams keeping the systems patched, but is necessary because software requires different toolchains. It would be nice if Jenkins supported plugins on a "per tenant" basis, even though the running version would still be one-per-instance. Some platforms (such as OpenShift) get around this by running Jenkins inside a container, but that leaves out Windows slaves.,8,Low investment: As the software is open source, there is no purchase required for on-premises installations, and there is a low barrier to entry for companies offering hosted solutions. This leads to competition on price, and therefore lower prices. Saves time by automating manual tasks: There are often a lot of repetitive tasks that need to be done to prepare for a release, and Jenkins enables these tasks to be run easily and frequently (for example, running tasks on every pull request) Near-immediate returns: Spend a day or two and easily automate most common tasks. Reports are visible so that managers and team leads can keep an eye on code quality.,Docker, OpenShift and Travis CIJenkins is a flexible Open Source CI/CD tool.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.,8,Good ROI as we can have automated executions on new build Faster feedback about product quality Supported all the platforms,TeamCity,M-Files, SoapUI NG Pro, TeamCity, Microsoft AzureJenkins helps automating everything manualWe have been using Jenkins across the company. The infrastructure provided by Jenkins allows us to automate our build process. The ability to work with numerous plugins makes it super easy to change various parts of the manual process to be fully automated. This reduces the level of effort engineers need to put in.,UI for displaying test results Detailed logs Easy segmentation of build processes,Make it easy to search logs across builds Provide wrappers to replicate jobs across multiple products Provide ability to export data,10,It reduces build times It increases developer productivity It could end up creating silos of engineering expertise,Travis and Chef,GitHub, Sauce Labs, SlackJenkins - monkey that needs to be tamedJenkins 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,6,Provide visibility into quality of deliverables Instant feedback Allows quick turn around of fixes,TeamCity and Bamboo,Gitlab, IntelliJ IDEA, IntelliJ WebStorm, JIRA Software, Atlassian ConfluenceAmazing CI ToolJenkins 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.,10,Consistent builds using the same dependencies and same steps every time. Much better than building on a developer's machine.,Microsoft Team Foundation Server,JIRA Software, Collaborator Community, Atlassian ConfluenceGo for jenkinsWe are mainly using jenkins to automate many parts of out software development life cycle like: - Build artifacts after commits - Run integration tests - Deploy artifacts,It allows to use plugins for integrating Jenkins with tons of programming languages. Good way to manage credentials in a centralized way. Clustering. Cross platform and easy to be installed. Nice UI to build pipelines, it has a minimalistic UI which is very intuitive. Good notification system that allows to be integrated with Slack, HipChat and other chats that allows to the team be aware of the status of the Jenkins jobs.,Graphic representation for the pipelines.,10,The inversion is low, you only need to provision a server but after that the automation stuff allow us to avoid headaches with distributed teams.,,Slack, IntelliJ IDEA, IntelliJ WebStorm, TSheets, Docker, AWS Elastic Beanstalk, AWS Lambda, Puppet Data Center Automation, VagrantJenkins ReviewJenkins 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 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.,8,Jenkins offers automated orchestration for workflows that would have to be manually executed otherwise. Personnel cost is always going to be higher than tools, and hence this is a huge cost benefit. Jenkins is free, so does not add to the infrastructure cost, unless you purchase the CloudBees distribution. Jenkins is well-known in the industry and hence training cost is bare minimum.
Unspecified
Jenkins
225 Ratings
Score 8.5 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>TRScore

Jenkins Reviews

Jenkins
225 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.5 out of 101
Show Filters 
Hide Filters 
Filter 225 vetted Jenkins reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role

Reviews (1-25 of 44)

  Vendors can't alter or remove reviews. Here's why.
Dylan Cauwels profile photo
March 14, 2019

Review: "Jenkins: The CTCI tool we've all been waiting for"

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
March 21, 2019

Jenkins Review: "Simple but powerful opensource CICD tool"

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
Erlon Sousa Pinheiro profile photo
February 26, 2019

Jenkins Review: "An amazing tool, but far from being perfect (unfortunately)"

Score 9 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
Mark Carpenter profile photo
February 07, 2019

Review: "Jenkins: The defacto standard build tool"

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
March 28, 2019

Jenkins Review: "Let your workforce interact by keeping them on same page!"

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
May 04, 2019

Review: "Jenkins is quick to learn and quick to implement"

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
November 28, 2018

Review: "Jenkins - Best Open-Source Continuous Integration Software on the market"

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
September 07, 2018

Review: "Jenkins as my Continuous Integration tool of choice"

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
June 26, 2018

Review: "Jenkins - when you want a dedicated, non SaaS CI/CD"

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
Kevin Van Heusen profile photo
April 09, 2018

Review: "Jenkins provides solid support for Continuous Integration and Continuous Delivery"

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

User Review: "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

Jenkins Review: "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
No photo available
July 06, 2018

Jenkins Review: "Automate anything and everything with Spinnaker"

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
January 23, 2018

Review: "Jenkins turns time-consuming tasks into automated successes"

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
April 12, 2018

"Quick review of Jenkins"

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
March 16, 2018

User Review: "Automate your environment with Jenkins"

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
No photo available
July 05, 2018

User Review: "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
No photo available
February 28, 2018

"Jenkins Review"

Score 8 out of 10
Vetted Review
Verified User
Review Source
It is being used by mostly the technology department. It allows us to run jobs between engineers and non-engineers. It increases productivity by automating processes.
  • Automated scheduled jobs
  • I think the UI is not the greatest.
It is well suited for kicking off a job manually or running automated jobs. I do see the use of a product such as this for business type folks, however, the UI is not that business friendly, rather more engineer friendly.
Read this authenticated review
Jonathan Yu profile photo
November 13, 2017

Jenkins Review: "The venerable open source build tool trusted by companies large and small"

Score 8 out of 10
Vetted Review
Verified User
Review Source
I used Jenkins to manage both development and release builds of software at my two previous roles (IBM and Red Hat.) In both cases, each department had its own instances, so that plugins could be customized and managed on a per-team, per-product basis. It enables teams to manage a fleet of build servers (slaves in Jenkins parlance) that can build source code and run tests in an automated fashion, across platforms - this enables cross-platform software to be tested against various versions of Windows and Linux, for example. It can also be used for simple automation tasks, though other tools like Ansible are better suited for those tasks.
  • Minimal but extensible and flexible: Out of the box, Jenkins provides rudimentary capabilities to manage a host system with a framework for running build tasks and installing tools. There are many extension points available for plugins, and so a rich ecosystem of plugins is available. Many version control systems are supported, and integrations with other tools through plugins is excellent.
  • Cross-platform: Supports many platforms and architectures quite easily, thanks to its implementation in Java
  • Design focus: With Blue Ocean, you can get a nice-looking web interface for free
  • Rich ecosystem: As Jenkins has been around for quite some time, there is a rich ecosystem of blogs, tutorials, guides, and documentation available for performing most of the day-to-day tasks you would need. There are also various vendors like CloudBees that offer hosted services.
  • Ease of deployment: Jenkins can be deployed quite easily as a standalone JAR file. There are also system packages available for many Linux operating systems, such as Debian.
  • Difficult to manage build configurations: builds are generally configured through the user interface, which is easier to modify (especially for casual users rather than dedicated release engineers), but this results in changes that can be difficult to track, especially if multiple people have write access to the system. Some teams manage this by restricting people that can modify builds, but this creates a bottleneck. Ideally, the system would provide a good audit trail and change history, allowing changes to be tracked and reverted easily. Competing offerings get around this by version-controlling their configuration (e.g. Travis CI, Drone, AppVeyor) but this results in a slightly higher learning curve.
  • Quality of plugins varies widely: plugins are in various states of maintenance, and some are woefully incomplete and no longer updated. It can be difficult to know whether a plugin is well-written or not, or even actively maintained.
  • Builds are often not easily reproducible: By default, builds are run on the slave systems, which can retain state between runs that cause difficult-to-debug failures. It's possible to get around this by using VM snapshots and periodically reverting to clean systems, or by using the Docker plugin to run builds inside ephemeral containers.
  • Plugins are globally scoped: Because plugin versions and the Jenkins version are per-installation, companies with multiple teams typically run multiple instances of Jenkins. This leads to a maintenance nightmare and a lot of duplicated effort across teams keeping the systems patched, but is necessary because software requires different toolchains. It would be nice if Jenkins supported plugins on a "per tenant" basis, even though the running version would still be one-per-instance. Some platforms (such as OpenShift) get around this by running Jenkins inside a container, but that leaves out Windows slaves.
Jenkins works pretty well for what it does, is easy to use, and aggregates logs as you would expect. For simple builds (especially Java builds), Jenkins works fairly well. It can run on full systems or headless systems, so tests requiring a graphical interface (such as those driven by Selenium and the WebDriver API) have no issues running. It can be used to manage systems to some extent (installing and managing software across a cluster by SSHing into slave machines) but its ecosystem is not geared for that; for a general automation solution, look to Ansible instead.
Read Jonathan Yu's full review
Deva Veluchamy profile photo
December 11, 2017

Review: "Jenkins is a flexible Open Source CI/CD tool."

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
Mohit Goenka profile photo
November 09, 2017

Review: "Jenkins helps automating everything manual"

Score 10 out of 10
Vetted Review
Verified User
Review Source
We have been using Jenkins across the company. The infrastructure provided by Jenkins allows us to automate our build process. The ability to work with numerous plugins makes it super easy to change various parts of the manual process to be fully automated. This reduces the level of effort engineers need to put in.
  • UI for displaying test results
  • Detailed logs
  • Easy segmentation of build processes
  • Make it easy to search logs across builds
  • Provide wrappers to replicate jobs across multiple products
  • Provide ability to export data
Jenkins is very well suited if you have a manual push process and are trying to automate it. This would help reduce the work load engineers have. Note that it is important for the process to be driven by scripts. If the build process is based on manual configurations and approvals, Jenkins wouldn't be very useful.
Read Mohit Goenka's full review
Stanislaw Wozniak profile photo
September 29, 2017

Review: "Jenkins - monkey that needs to be tamed"

Score 6 out of 10
Vetted Review
Verified User
Review Source
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
More stability and job templates would make Jenkins a serious competitor in the CI space
Read Stanislaw Wozniak's full review
Linda McDonald profile photo
August 29, 2017

Jenkins Review: "Amazing CI Tool"

Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
Jenkins is a wonderful tool for all levels of developers allowing many plugins to be added and scripts can be written to account for any customizations needed. I am not familiar with the pipelines functionality but hope to start using it soon for continuous delivery.
Read Linda McDonald's full review
Rene Enriquez profile photo
November 14, 2017

User Review: "Go for jenkins"

Score 10 out of 10
Vetted Review
Verified User
Review Source
We are mainly using jenkins to automate many parts of out software development life cycle like:
- Build artifacts after commits
- Run integration tests
- Deploy artifacts
  • It allows to use plugins for integrating Jenkins with tons of programming languages.
  • Good way to manage credentials in a centralized way.
  • Clustering.
  • Cross platform and easy to be installed.
  • Nice UI to build pipelines, it has a minimalistic UI which is very intuitive.
  • Good notification system that allows to be integrated with Slack, HipChat and other chats that allows to the team be aware of the status of the Jenkins jobs.
  • Graphic representation for the pipelines.
Jenkins is good when:
- You want to automate your build pipelines
- Implementing continuous delivery process
- Automate manual tasks

Jenkins is not good when:
- You have your code in GitHub, I will rather use travis instead which is already included and well integrated
- You want to see in a graphic representation of your pipeline, in this cases another tools like GoCD would be a fit
Read Rene Enriquez's full review
Juni Mukherjee profile photo
July 21, 2017

"Jenkins Review"

Score 8 out of 10
Vetted Review
Verified User
Review Source
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 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.
Jenkins addresses most use cases.
Read Juni Mukherjee's full 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