--- description: Jenkins : avantages et inconvénients. Lisez les avis clients, consultez les prix et découvrez les fonctionnalités. image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: Jenkins - Avis, notes, prix et abonnements - Capterra Canada 2026 --- Breadcrumb: [Accueil](/) > [Outils intégration continue](/directory/31119/continuous-integration/software) > [Jenkins](/software/171026/jenkins) # Jenkins Canonical: https://fr.capterra.ca/software/171026/jenkins Page : 1/24\ Suivant: [Page suivante](https://fr.capterra.ca/software/171026/jenkins?page=2) > Serveur d'automatisation open source offrant de nombreux plug-ins pour la création, les tests et le déploiement de logiciels. > > Conclusion : 568 utilisateurs lui ont donné la note de **4.5/5**. Figure au meilleur classement pour **Probabilité de recommander le produit**. ----- ## Statistiques et notes | Métrique | Notation | En détail | | **Note globale** | **4.5/5** | 568 Avis | | Simplicité | 4.1/5 | D'après l'ensemble des avis | | Support client | 4.0/5 | D'après l'ensemble des avis | | Rapport qualité-prix | 4.6/5 | D'après l'ensemble des avis | | Fonctionnalités | 4.5/5 | D'après l'ensemble des avis | | Pourcentage de recommandation | 90% | (9/10 Probabilité de recommander le produit) | ## À propos du vendeur - **Entreprise**: CloudBees - **Fondé**: 2011 ## Contexte commercial - **Type de licence**: (Version gratuite disponible) - **Public cible**: Travailleur autonome, 2–10, 11–50, 51–200, 201–500, 501–1 000, 1 001–5 000, 5 001–10 000, 10 000+ - **Déploiement et plateformes**: Cloud, SaaS, web, Mac (ordinateur), Windows (ordinateur), Linux (ordinateur) - **Langues**: anglais, chinois - **Pays disponibles**: États-Unis ## Fonctionnalités - Automated Testing - Débogage - Déploiement continu - Gestion de versions - Gestion des pipelines - Livraison continue ## Intégrations (8 au total) - Acunetix - Bitbucket - Gatekeeper - GitHub - GitLab - Jira - Microsoft Azure - Slack ## Ressources d'aide - Service client/courriel - FAQ/forums - Base de connaissances - Support téléphonique ## Category - [Outils intégration continue](https://fr.capterra.ca/directory/31119/continuous-integration/software) ## Logiciels similaires 1. [GitHub](https://fr.capterra.ca/software/129067/github) — 4.8/5 (6155 reviews) 2. [GitLab](https://fr.capterra.ca/software/159806/gitlab) — 4.6/5 (1215 reviews) 3. [Bitbucket](https://fr.capterra.ca/software/157785/bitbucket) — 4.6/5 (1343 reviews) 4. [AWS CloudFormation](https://fr.capterra.ca/software/205397/cloudformation) — 4.5/5 (106 reviews) 5. [SonarQube](https://fr.capterra.ca/software/210481/sonarqube) — 4.5/5 (66 reviews) ## Avis ### "Great CI Software" — 5.0/5 > **Mike** | *11 septembre 2025* | Matériel informatique | Taux de recommandation : 10.0/10 > > **Avantages**: Incredibly powerful CI tool that allows us to be able to run developer test and integration test during different phrase of the dev process. The software is open source so you can easily customize it. All the community contribution went into jenkins made the software an incredible value for money > > **Inconvénients**: Jenkins uses their own DSL for configuring their job script, which has a high learning curve and is not the most intuitive. They could consider integrating other scripting languages if possible. Some upgrade and downgrade run into plugin incompatibility issue which is annoying. > > Overall Jenkins is an excellent software that works well with our developer workflow. I am a big fan. ----- ### "The Industry Standard for Flexible, Enterprise-Grade CI/CD Pipelines" — 5.0/5 > **Utilisateur vérifié** | *23 janvier 2026* | Administration publique | Taux de recommandation : 10.0/10 > > **Avantages**: The strongest feature is the Master-Slave architecture, which allows us to distribute heavy build workloads across multiple agents efficiently. I also rely heavily on Jenkins Pipelines (Jenkinsfile) to define our entire build-and-deploy process as code, which supports our agile development cycle perfectly. The sheer number of plugins available means I can integrate it with almost anything in our stack, from Docker and Kubernetes to SonarQube and Artifactory. > > **Inconvénients**: The user interface (UI) feels a bit dated compared to newer tools like GitLab CI or CircleCI. Also, managing plugins can sometimes be a headache, specifically 'dependency hell' where updating one plugin breaks another. It requires careful maintenance to keep the controller stable. > > I have used Jenkins extensively to orchestrate end-to-end CI/CD infrastructure for highly secure government and financial environments. It serves as the backbone of our automation, handling everything from code checkout (Git/Bitbucket) to Docker image creation and deployment to Kubernetes clusters. While it requires some maintenance effort, its flexibility and control are unmatched for complex, custom enterprise workflows. ----- ### "Reliable CI/CD Tool with Great Automation Capabilities" — 5.0/5 > **Parth** | *13 octobre 2025* | Services et technologies de l'information | Taux de recommandation : 10.0/10 > > **Avantages**: Jenkins is invaluable for automating the entire CI/CD pipeline. It integrates well with my Bitbucket, Maven, and Selenium and making it easy to trigger builds and run automated tests whenever there’s a code change. > > **Inconvénients**: What I dislike most about Jenkins is that managing and maintaining multiple Jenkins jobs can become complex over time. > > Overall, I really like Jenkins for its ability to automate the CI/CD process and integrate with all the automation tools, ensuring continuous testing and faster delivery. What I like least is that it can become a bit complex to maintain when there are many jobs and plugins involved. But with proper configuration and pipeline as code, those challenges can be managed effectively. ----- ### "bad UI but good functionality" — 4.0/5 > **Michal** | *28 février 2025* | Comptabilité | Taux de recommandation : 7.0/10 > > **Avantages**: Jenkins does what it needs to do. If the dev-ops team sets it up correctly the builds occur as expected. > > **Inconvénients**: Jenkins has a really outdated UI, it is kind of hard to navigate and know where everything is, but once you get used to it it is fine. > > In general we use jenkins often, and it deploys our software without too much trouble ----- ### "Using Jenkins in managing CI/CD process" — 5.0/5 > **Jim** | *28 novembre 2025* | Télécommunications | Taux de recommandation : 10.0/10 > > **Avantages**: Jenkins is super powerful and ease to use in CI/CD, it can integrate all critical phases in checking out, building, testing and delivery. > > **Inconvénients**: The plugin management is still complicated and required lots of rebooting, for example. If I forgot to install git plugin, I will need to reinstall it and reboot the whole Jenkins. > > I already used Jenkins since 2012, it is my first priority in CI/CD, it can be easily used in personal projects in container, as well as big corporate level IT projects. ----- Page : 1/24\ Suivant: [Page suivante](https://fr.capterra.ca/software/171026/jenkins?page=2) ## Liens - [Afficher sur Capterra](https://fr.capterra.ca/software/171026/jenkins) ## Cette page est disponible dans les langues suivantes. | Langue | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ko | | | nl | | | nl-BE | | | pt | | | pt-PT | | ----- ## Données structurées