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.

Powerful CICD tool to handle all stage in pipeline

Commentaires : 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.

Avantages :

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.

Inconvénients :

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.

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.

Widely adopted and flexible open source tool

Avantages :

Best open source that allows you to manage your jobs with the support for multiple plugins for free.

Inconvénients :

Time taking to setup few workflows. Updates are very frequent

Versatile program with important features

Commentaires : An experience of average satisfaction, we did not like that we had to spend extra budget to hire a new software that would bring together the capabilities that Jenkins could not contain enough for our team to feel comfortable, but on the other hand we do accept that it has improvement systems that They improved our developed software.

Avantages :

A program that in the team generated high expectations for generating build automation, where Jenkins can be configured to automatically execute software builds every time changes are made to the source code, this ensures that any new code integration is tested and verified instantly, making it easy to detect and fix early errors or compatibility issues.

Inconvénients :

Under support for Microservices, which in our case and given that our company Google operates at large scale, often with architectures based on microservices, Jenkins could not handle multiple projects and microservices simultaneously, not allowing independent and specific builds and deployments as required. We needed, in this sense, we had to use a program similar and added to the one we already had.