Jenkins Review

PROS: Jenkins offers wide range of language support and flexible build pipelines. You can easily define jobs with elastic hooks and integrate it with multiple SCM systems.

CONS: They could improve the UI design and add more responsive design and material style.

PROS: It is free to set up, and you can use it in every project. It offers lot of features and the tool is easy customizable. I like that it provides reports, graphical representation of current status or current jobs and I like that it keeps archive of and longs. You can even configure access rights for users.

CONS: They could make the platform even more comfortable and to include advance features.

PROS: Jenkins doesn’t have learning curve. As a developer I’m using this IT management software for years and it doesn’t take much time to figure out how it works or how to do something. With this solution creating new builds is extremely easy and even debugging builds is effortless. If the build is broken, all you have to do is to read the logs or run the build conf script inside the environment.

CONS: The UI looks outdated even though it works fine. They could ad few fields for the default cases instead of shift through all fields in order to find common variables.

PROS: Jenkins offer complete continuous integration system that allow you to automate all your development processes in few minutes. Its plugins system allows you to do everything you can imagine. Jenkins is easily scalable and fast processing the workflows. The dashboard is great for managing and displaying the running processes. Also, I like that this tool integrates with lot of communication tools such as: Slack, IRC channels, SMS Service and Time Tracker.

CONS: Jenkins is Java based product it requires Java stack available in order to run Jenkins, and this can be a problem if you are not having Java operations.

PROS: First thing that I like about this product is the fact that it is an open source and free to use. It has large community so we don’t have to search around whenever we have questions about the product. I have seen that lot of teams start their continuous integration with Jenkins and move to paid build system.

CONS: What I don’t like is that the tool doesn’t follow latest design trends and there are other similar solutions that are far more intuitive than this one.

PROS: Jenkins is great CI/CD solution, it offers plugins for everything and they are not difficult to create. I like that it supports Windows, Mac and Linux and this means that all build configurations are consistent and reports are available directly from dashboards. Also, there is commercial support from CloudBees and other companies. It doesn’t require databases and the upgrades are straightforward. You can use its plugins to manage slave machines and you can even manage system-level tools.

CONS: Jenkins looks bit out dated and I don’t really like its design. Also, the build configurations are kept separate from version control.

PROS: I like that there are configurations for everything into Jenkins. The good thing is that whenever you need a new build for a new Git repo you can always set it to default and let it run. You can even configure each small detail and start working on what you want.

CONS: The good thing about this tool is that everything is configurable but this may be even negative thing because if something goes wrong you have to look at the configurations and to read each line in order to find where the issue is.