Jenkins Reviews

Jenkins is an incredibly versatile and reliable tool for continuous integration and continuous deployment (CI/CD). As a senior automation tester, I appreciate its seamless integration with various version control systems, making it easy to trigger automated tests whenever new code is pushed by a developer. The extensive plugin ecosystem allows for significant customization and expansion of its functionalities. One of my favorite features is its ability to expose Allure reports, providing detailed and visually appealing test result reports that are easy to share with stakeholders.

While Jenkins is a powerful tool, it can be quite complex to set up and configure, especially for those who are new to it. The user interface, although functional, feels outdated and can be cumbersome to navigate at times. Additionally, managing a large number of plugins can sometimes lead to compatibility issues and maintenance overhead.

The software itself is stable, it runs well and is not too complex to install

The fact that pipelines are built either with a UI which makes the pipeline tough to read when you have lots of conditions.

The groovy language can also be used to write pipelines, but really ?? Let’s use a more common scripting language for this, maybe Python or ruby.

Jenkins automates my build and deployment process, saving me a ton of time. My code gets tested and deployed automatically after each commit.

Configuring the initial setup and understanding all the plugins took quite a bit of time.

It is a great CICD tool, allowing easy integration with VCS tools, and jobs scheduling. Plugins are essential for its use

Upgrades sometimes get your system down and rollback is required when using On Prem

It is highly extensible and It is easy to use.

It can be a security risk - Jenkins is a web application, so it is susceptible to security attacks.

I like Jenkins because it allows me to automate and streamline my software development workflow, making me more productive and efficient. Also Jenkin is open-source which makes it more cost effective.

Jenkins relies heavily on plugins to extend its functionality. However, managing and updating plugins can be time-consuming and complex.

It’s open source, well known and well supported software.

Nothing that comes up to my mind as a con to jenkins.

I loved Jenkins for its extensibility, flexibility, and automation capabilities. With a wide range of plugins and integrations, I could customize it to fit my needs perfectly. Jenkins automated repetitive tasks, making our development process more efficient. It scaled effortlessly, handling projects of all sizes. The active community support and seamless integration with other tools were also fantastic. Jenkins significantly improved our development workflow.

I found a few challenges with Jenkins. Firstly, there was a steep learning curve, especially for beginners. Managing installations and plugin updates could be time-consuming, and the user interface felt outdated. Scaling Jenkins and troubleshooting issues were sometimes difficult. However, the community support and documentation were helpful in addressing these challenges.

I like it's flexibility. You can almost do whatever you want with it.

Plugins can be outdated, also documentation should be fixed. I also hate that there is no way to configure Jenkins with Database backend (everything is kept in files). Because of that there is no way to create multiple Jenkins instances.

Jenkins is fully open source, making it easy to install on almost any system.
Jenkins comes with many different plugins that allows you to use it with your favorite Engine, versioning solution, etc...
Jenkins offers many different ways of creating builds scenario, easy to understand steps, and strong scripting

It's not always easy to find support, and you might need to rely on your web searching skills in order to find some help.
Updates can sometimes break plugins so you need to be careful with those. Luckly enough, there are ways to revert updates if necessary.
It's not for Everyone, since setting up a server could take time and a lot of trial and errors.

The build monitoring and deployment automation are the key features for me. It also integrates well with version control.

I like the quick build layout and UI better

First of all, it's an open-source tool. We need appreciate the efforts of Jenkins team. It's very stable and has a lot features on top of it. Also writing pipelines with groovy language is quite straightforward.

Jenkins can improve the UI and its elements. It can provide more clear UI for the users.

Jenkins allows us seamlessly switch back and forth between our clients to parse through their data.

We only use Jenkins for one purpose and it allows for that, so there isn't any con that I have.

Most of the IT companies are using jenkins to automate the SDLC that means automating steps like build, test and deploy. With jenkins we can build pipelines with customized workflows to automate. This gives high security and integrate with other tools like AWS and kubernetes. A very flexible tool that I use to enhance the quality of a software.

I had to learn and ask from community to learn things. So for a new comer cannot use jenkins without a technical knowledge.

Most of the IT companies are using jenkins to automate testing, building and deployment stages of the code. We can configure jenkins to automatically trigger these steps when code merge happens to the repository. If the deployment or build got failed, I go through the jenkins logs and find the issue. There's a big community support for jenkins and we can get tech help from them.

Jenkins need considerable memory, CPU and storage resources of the server to run.

It was a revolutionary tool for Ci/Cd with a big community developing new plugins

it's outdated compared to other tools and way to annoying to maintain

Building up Devops is very easy using Jenkins and get integrated with any existing build mechanism

Jenkins visual appearance that could be improved and better organized

Installation was easy, and the pipelines work religiously well. Executors handle Java memory allocation well. Love the plugins. You don't have to know how to write code to use some of the popular ones. I didn't use the cloud hosted option, but I know people who have who love it.

Some of the authentication stuff is a little confusing, but if you're on a small team it's probably easier to keep your installation secure that if you use it for a large organization with oAuth or SSO.