Jenkins facilitates continuous integration and continuous delivery in software projects by automating parts related to build, test, and deployment. This makes it easy for developers to continuously work on the betterment of the product by integrating changes to the project.

Why Jenkins is not good?

4. Poor visibility into Jenkins installs and projects creates chaos, can disrupt work, and increases risk. Unlike dedicated CI/CD tools, Jenkins does not have “applications” or “releases.” Instead, everything has to be its own project (what used to be called jobs).

Does anyone still use Jenkins?

It is one of the most trusted and well-known open-source tools. Jenkins is used for building and testing software projects continuously which makes it easy for developers to integrate changes in a project. ... In general Jenkins as a tool still holds value for following use-cases: You are using an on-premise solution.