Filter Ratings and Reviews
Filter 286 vetted Jenkins reviews and ratings
Reviews (1-25 of 51)
Companies can't remove reviews or game the system. Here's why.
We use Jenkins as our build management software, and it is mostly used between the development and QA teams. We use it both in manual and automated builds. It allows the developers to work together and send a combined solution to the QA team. It also controls our versioning with minor builds and patches.
- Automated build process
- Great process control
- Good notifications to groups
- Can be difficult to configure
- Not the best error reporting
October 16, 2019
We used Jenkins as our build server to execute build jobs and automated tests. The whole of engineering used it to build jobs and checking build status. Ensuring their branches would successfully run tests before merging to the master branch. It was a cheaper alternative to non-open-source competitors since it was free.
- Pluggable.
- Extensible.
- Large development community.
- It's not cloud-based.
- It can be hard to figure out.
- High learning curve.
- Have to maintain infrastructure yourself.
September 01, 2019
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.
We use Jenkins as our main CICD server for multiple projects in our department and integrate Jenkins with our Gitlab source code repository and other tools such as SonarQube, Artifactory, Tomcat, Jboss, and Coverity. Our development team uses Jenkins jobs on every check-in code to run unit tests, scan code quality and run automation tests on every merge request before actually merging. Jenkins helps to increase our quality of product and eliminate most manual steps on deployment and integration.
- Flexible to create jobs in freestyle or pipeline.
- Supports various plugins to work with different programs such as AWS, Azure, Linux, Powershell, etc.
- Gives you a centralized location to manage all project pipelines and build information.
- Support various ways to trigger new jobs.
- Allows us to edit and retain files in the server and not override by repository.
- Support cluster to increase build performance.
- Jenkins UI is too simple.
- Does not provide a feature for backup and restore jobs.
- Lack of authorization rule - We could not assign separate users or groups to separate views or jobs.
Jenkins is the main workhorse supporting our build and deploy pipeline and is used by both developers and dev-ops alike. Jenkins provides a sort of single source of truth by running tests and verification steps to ensure that code going out to production is functional and safe. It also allows our team of over 100 developers to safely deploy production changes many times per day.
- Highly configurable to individual needs
- Many available plugins and integrations
- Support for many different languages
- UI feels outdated and unintuitive, especially to newer users.
- User management is too simple.
Jenkins is used across various teams in our organization. It is an integration tool where we use the CI/CD pipeline for continuous deployments of our microservices. This tool makes life easy to automate the process of deploying services into all environments ( staging, production, and development environments). It uses in all development life-cycle processes including build, document, test, package, stage, deploys, static analysis, and publishing.
- It is free of cost.
- Easily configurable - Jenkins can be easily modified and extended. It deploys code instantly, generates test reports. Jenkins can be configured according to the requirements for continuous integrations and continuous delivery.
- Easy support - Because it is open source and widely used, there is no shortage of support from large online communities of agile teams.
- Most of the integration work is automated. Hence fewer integration issues. This saves both time and money over the lifespan of a project.
- Jenkins management is generally done by a single user and that leads to tracking and accountability problems with the pushed code.
- Jenkins doesn’t allow one developer to see the commits done by another team member, readily. This makes tracking the overall release progress a rather difficult job for larger projects. This can cause a lot of trouble with the release manager.
- Jenkins doesn’t provide any analytics (there are plugins but they are not enough) on the end-to-end deployment cycle. This again goes back to the lack of overall tracking that contributes to the lack of analytics as well.
We are using Jenkins for our CI/CD solution. It is used across all the departments in our org. we use Jenkins for various purposes. We use it deploying applications to various environments and taking the backups of the servers and restore them. We integrated Jenkins with various tools across the whole organization.
- Scalable
- Lots of plugin support
- Integrates with almost every tool
- Sometimes a bit slow
August 05, 2019
[We're] Using Jenkins for CI/CD automation and enforcing quality gates.
- Rich plugin ecosystem
- Infinitely extendable via custom configuration
- Scalable thru multi node architecture
- First-class support for docker containers
- More modern runtime, without the Java overhead
- Better isolation for plugins via containers
March 14, 2019
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.
March 21, 2019
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.
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
- 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
February 07, 2019
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.
March 28, 2019
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.
May 04, 2019
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.
November 28, 2018
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.
September 07, 2018
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.
June 26, 2018
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 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.
April 09, 2018
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.
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
November 13, 2017
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 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:
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).
December 11, 2017
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.
November 09, 2017
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
September 29, 2017
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
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.
April 13, 2017
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.
Jenkins Scorecard Summary
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.
Categories: Continuous Delivery, Build Automation
Jenkins Integrations
Jenkins Pricing
- Does not have featureFree Trial Available?No
- Has featureFree or Freemium Version Available?Yes
- Does not have featurePremium Consulting/Integration Services Available?No
- Entry-level set up fee?No
Jenkins Technical Details
| Deployment Types: | SaaS |
|---|---|
| Operating Systems: | Unspecified |
| Mobile Application: | No |