Jenkins

Meilleur produit testé pour l'intégration continue

Avantages :

La richesse des possibilités d'utilisation est particulièrement apéciable. Son intégration avec d'autres produits est aussi très utile

Inconvénients :

La difficulté à programmer son utilisation et à mettre en place est un frein au début.

Jenkins is a must for Devops Engineer

Commentaires : It's one of the most important tools that I use every day while working as a DevOps Engineer. It has helped me in easing my job very much

Avantages :

We can automate and configure almost everything using jenkins, it can be used to start/stop servers, backup dbs, build and deploy codes in the environments, etc.

Inconvénients :

The complete logs may not be visible from Jenkins, but still, the main error can be seen. I can't think of any other problems in Jenkins

Easy to understand, ease of use, and sense of the operation of automation and scripting

Commentaires : As automation of script files and file execution, the feel of operation in the system is easy to understand. I started from a place I had never used, but it felt that way. In a nutshell, it is an image of the Linux Cron and Windows task scheduler. It is easy to manage problems that have been resolved, specific effects and CI/CD processing details. When the agent load increases, there is no need to respond manually; automatic escalation will distribute the load. The file (Jenkinsfile) describing the functions, points and CI/CD processing that contributed to the problem can also be managed in the Git repository as a set with the source code, so it is easy to check the processing details and modify the Jenkinsfile.

Avantages :

The amount of information in the search results is significant, and it is easy to operate because it is free (easy to stop in case of emergency). A Docker agent and JenkinsX are also available, so they are compatible with the latest technology. Because it can be used not only on-premises but also with Kubernetes, it is helpful because the learned technology can be used for a long time, even if the stage changes.

Inconvénients :

Since the configuration screen is displayed in a tabbed format, there are times when you cannot see what you want to edit unless you show it at the bottom of the browser screen.

One of the best CI/CD experience

Avantages :

- It has huge customisation options while creating a new CI/CD pipeline- It greatly reduces the developer effort by automating a lot of stuff- Great for running regular cron jobs

Inconvénients :

- The UI can be made much better - The erorr reporting in case of pipeline failures can be much better. One of the competitor which wins over Jenkins here is CircleCI

For all your CI/CD needs!

Commentaires : I use Jenkins primarily to run builds for all of our repos and execute a large number of automated tests. It is incredibly useful to manage CI tasks and activity across many repos.

Avantages :

I've been using Jenkins for several years and find it extremely useful in solving any CI scenario from easy to very complex. With its rich library of plugins and active community, it's relatively easy to develop and debug pipelines. I like that some plugins provide embedded pages within builds for things like test reports, commit history, etc. Jenkins can also be easily integrated with a large number of external applications.

Inconvénients :

In my experience with Jenkins, I find plugin management to be the most troublesome. It is often the case, that plugins are no longer maintained, lack documentation, or break things with upgrades.