Jenkins Pros and Cons
Having builds and test tasks triggered on commit helps not to break the product.
We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity.
We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable.
Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead.
Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes.
For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance.View full review »
It is very useful for us to be able to collect and manage automatic processing pipelines.View full review »
Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins.View full review »
Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc.View full review »
We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit.View full review »
We used it for all continuous integration parts, like automation testing, deployment, etc.View full review »
Distributed execution of build and test jobs.View full review »
It's very useful when you want to automate different processes from beginning to end.View full review »
The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle.View full review »
There are a large number of plugins available for integration with third party systems.View full review »
Jenkins relies on the old version of interface for configuration management. This needs improvement.
Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things.
Sometimes you have Jenkins restarting because of OOM errors.View full review »
The learning curve is quite steep at the moment.View full review »
Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on.View full review »
The bug fix speed is very slow.View full review »
In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS.View full review »
It does not have a very user-friendly interface.View full review »
The documentation on plugin development could be better: more examples. View full review »
Centralized user management would be helpful.View full review »
Better and easy-to-use integration with Docker would be an improvement.View full review »
The user interface could be updated a little.View full review »