We use Jenkins as the main CICD in our project, we organize jobs with similar function into Group, we create jobs for the build, compile, and unit test each time a developer check-in their code to a specified branch and build a new version of artifact when having master branch commit. We add some additional plugin and create Jenkins jobs for run system test, automation test, and integration test automatically when having new commit to master and have jobs for deploy our new code to destination VMs on demand.

Jenkins is very simple to installation and configuration as standalone or cluster, just a few clicks to get Jenkins ready, it is flexible and easy to create Pipeline and Job from UI or by YML file. Jenkins support many plugins allows it easy to integrate with other tool and software such as AWS, Sonar, JMeter... and Jenkins support almost major language and OS.

Jenkins UI is simple and it is hard for manage when we have a large number of jobs and pipelines. It does not have features for tracking job history, sometimes accident deletes or changes a job and we unable to recover it.

I have used Jenkins for few projects with team members, we used it because we needed more flexibility at configuration. It is the only choice when you need more control over integration and testing. It is hard to configure and install but that is the trade-off for control over customization and configuration. Jenkins is free of cost itself although you need to server to host it. We use Jenkins only for projects which require more configuration and security.

Currently Jenkins is the only CI tool which has the largest set of plugins, it gives you more control over how it should work, like you can customize pipeline of continuous integration and delivery. There are plugins allow you to run Jenkins in kubernetes and docker but we never ran it on containers. Huge number of plugins available for Jenkins which allow you to integrate with other tools and customize it to your needs, plugins are available at Jenkins update center. Great thing about Jenkins is it work on windows, Linux and mac OS. Cost of using Jenkins is free because its open source although you need server to host it, you must maintain and update and that's your responsibility.

Jenkins is not easy to use you need to configure it and host it before using unlike tools like travis CI which is ready to be used. Learning curve is steep because it has lot of features and customization which is little bit hard at start. Hosting server is needed to host Jenkins, which means you also need to pay for hosting. Maintenance and updation is user responsibility.

Nobody ever got fired for choosing Nagios as an IT monitoring tool, and nobody ever got fired for choosing Jenkins as a CI tool. However, both products are, in my estimation, relics from an age when better options really weren't available. Jenkins is free, widely used, and has a vibrant ecosystem. However, at this point, I feel certain that it's coasting on its past reputation. Before settling for Jenkins, I would carefully examine more modern products in this space such as GitLab CI.

Jenkins can be set up on-premise and comes with no licensing fees. Considering the cost of some CI platforms, that's a HUGE advantage. There are enough plugins that you can find added functionality for almost anything.

Jenkins can be kind of like WordPress - there is such heavy reliance on plugins that they can sometimes cause unexpected behavior when interacting with each other. Jenkins is significantly harder to get started with than something like GitLab CI. When tasked with creating pipelines for my own development projects, I opted for GitLab CI, and I feel like I'm missing absolutely nothing. The stock Jenkins interface is absolutely horrible. It looks like a leftover from 10+ years ago. (Another similarity with NAgios...)

Jenkins helps a lot with the CI/CD process of a company.

It is very easy to integrate a pipeline on Jenkins and the integration with GitHub is very useful.

When a build is launched on Jenkins sometimes the UI on Jenkins is not correctly refreshed, we need to constantly hit the browser refresh button to see the correct status of the build.

It’s not hard to setup your project in Jenkins

The long updates which can starts anytime

Best tool for deployment process , it providers clear cut view of the deployment status

Sometimes the deployment status won't get updated fast

1. First of all its open source and has a vibrant community2. Great plugin support3. Integrates well with Containers like Docker and Kubernetes4. Ease of pipeline management5. Reports are crisp and easy to understand6. Robust CI CD solution

No Cons so far. One improvement can be done is in its UI!!

Jenkins is a powerful tool for automating various software development tasks. Its user-friendly interface, integration capabilities, open-source nature, and wide range of plugins make it an excellent choice for software development teams. While setting up Jenkins can be a bit challenging and there may be compatibility issues, these drawbacks are outweighed by the benefits that the platform provides. In short, Jenkins is a must-have tool for streamlining your development workflow and improving your team's efficiency.

Jenkins provides a user-friendly interface to manage and automate various software development tasks. Integrates well with other tools and systems, making it easier to manage the entire development process. The open-source nature of Jenkins makes it accessible and customizable to fit the specific needs of your team.

Setting up Jenkins can be a bit complex and time-consuming, especially for those who are new to it. The platform can become a bit slow and unresponsive when handling large projects with multiple jobs.

Easy to get started. Can be treated as a starter pack for modern CI/CD.

Not much needed to get started on a project. Also, we can keep an eye on monitoring and metrics while using Jenkins

The UI needs to be improved. A modern user-friendly documentation can help.

I loved Jenkins he was the old Alexa or Siri he made life so much easier

Nothing I love Jenkins he is the old school Alexa

I'm running multiple backup or VM configuration tasks. I like it, but I also see potential issues in the future. Because of that I will think about migrating to another solution in the future.

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.

It has helped me achieve so many things with so little knowledge. It is the heart of my orchestration system built for a very large distributed system as a software engineering intern. Because of it's reliability, it is still being used as that. Very easy to use and mixing with your creativity you can achieve almost anything .

Ability to perform any kind of deployment/orchestration.

Security Vulnerability. It can be attacked from multiple places.

I use jenkins daily as a build and deployment tool in an enterprise software setting.

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

Is widely used in the company and is very stable. maybe complex to manage, but is very good for CI and CD

Is the most used tool of the market, besides the open source to have a very active community.

I believe that only the UI could improve

Jenkins has been a great tool for maintaining build version and scheduling timely jobs

Jenkins plays a important role in product development and deployment lifecycle, where a developer can build his code and give the build version to QA for testing, ones the build is tested it can be signed off and deployed to prod, Not one but many Different Applications can be created and can be built and maintain the build versions of each applications, Ad-Hoc scripts can be managed and can be triggered when required or schedule it in a timely manor, the jobs can be parameterised or non-parameterised, and can even set default parameter value, The scheduling of jobs are done using cron string, Usually we use linux shell scripts for job build configurations, it can also be done by many different ways. We can configure different executor machines for different jobs to distribute the load, Supports parallel processing of different jobs at the same time, User permissions are manageable (read, write, build etc.. ), It has lot's of native and third party plugins, for achieving different use-cases, and lot of community support, The features are well-documented inline, it has a great version control of the job configuration

Scheduling becomes little complicated if the job has to run in un uniform interval of time, for which we had to set up two jobs with the same build configuration and different cron scheduler, sometimes the application dropdown values disappears when used with different executors , Not a fully cloud-based solution, infrastructure should be managed internally, maintains limited build history,

Jenkins is a great tool for DevOps professionals, and I am really satisfied with my experience.

It's very easy to integrate plug-ins for automated deployment and automated testing. It is easier to fix build and report errors in jenkins.

Jenkins doesn't come up with too many features out of the box, so managing individual plug-ins over time becomes difficult.