--- description: ¿Qué piensan los usuarios de Jenkins? Lee las reseñas y opiniones verificadas, descubre sus características y el nivel de usabilidad, consulta los precios y conoce las ventajas y desventajas de Jenkins gracias a Capterra República Dominicana. image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: Jenkins - Opiniones, precios y características - Capterra República Dominicana 2026 --- Breadcrumb: [Inicio](/) > [Herramientas de integración continua](/directory/31119/continuous-integration/software) > [Jenkins](/software/171026/jenkins) # Jenkins Canonical: https://www.capterra.do/software/171026/jenkins Página: 1 de 24\ Siguiente: [Página siguiente](https://www.capterra.do/software/171026/jenkins?page=2) > Servidor de automatización de código abierto que ofrece una gran cantidad de complementos para la creación, prueba e implementación de software. > > Veredicto: 574 usuarios lo han valorado con **4.5/5**. De los mejores valorados en **Probabilidad de recomendación**. ----- ## Estadísticas y valoraciones rápidas | Métrica | Calificación | Detalles | | **En general** | **4.5/5** | 574 Opiniones | | Facilidad de uso | 4.1/5 | Basado en las opiniones generales | | Asistencia al cliente | 4.0/5 | Basado en las opiniones generales | | Relación calidad-precio | 4.6/5 | Basado en las opiniones generales | | Funcionalidades | 4.5/5 | Basado en las opiniones generales | | Porcentaje de recomendaciones | 90% | (9/10 Probabilidad de recomendación) | ## Sobre el proveedor - **Empresa**: CloudBees - **Constitución**: 2011 ## Contexto comercial - **Modelo de precios**: (versión gratuita disponible) - **Público objetivo**: Trabajador autónomo, 2-10, 11-50, 51-200, 201-500, 501-1,000, 1,001-5,000, 5,001-10,000, 10,000+ - **Despliegue y plataformas**: Cloud, SaaS, Web, Mac (desktop), Windows (desktop), Linux (desktop) - **Idiomas admitidos**: chino, inglés - **Países disponibles**: Estados Unidos ## Funcionalidades - Automated Testing - Control de versiones - Depuración - Entrega continua - Gestión del pipeline - Implementación continua ## Integraciones (en total: 9) - Bitbucket - Gatekeeper - GitHub - GitLab - Invicti Web + API (formerly Acunetix) - Jira - Microsoft Azure - Slack - SonarQube ## Opciones de asistencia - E-mail/Help Desk - Preguntas frecuentes/foro - Base de conocimientos - Asistencia telefónica ## Categoría - [Herramientas de integración continua](https://www.capterra.do/directory/31119/continuous-integration/software) ## Alternativas 1. [GitHub](https://www.capterra.do/software/129067/github) — 4.8/5 (6206 reviews) 2. [Bitbucket](https://www.capterra.do/software/157785/bitbucket) — 4.6/5 (1350 reviews) 3. [GitLab](https://www.capterra.do/software/159806/gitlab) — 4.6/5 (1227 reviews) 4. [SonarQube](https://www.capterra.do/software/210481/sonarqube) — 4.5/5 (68 reviews) 5. [Jira](https://www.capterra.do/software/19319/jira) — 4.4/5 (15494 reviews) ## Opiniones ### "Flexible automation platform with strong testing capabilities" — 4.0/5 > **Nikitha** | *5 de septiembre de 2026* | Software informático | Valoración de la recomendación: 10.0/10 > > **Puntos a favor**: Jenkins provides useful Features for automating software development and testing workflows. It can support Project Management by helping teams organize and monitor automated builds and deployments. The platform is also useful for Team Collaboration because developers and other technical team members can share build information and track workflow status. Once configured properly, Jenkins can make recurring development and Testing tasks more efficient. Overall, it provides good Value for Money for teams that need a flexible automation platform. > > **Puntos en contra**: The main drawback is the Ease of Use, especially for new users. Setting up pipelines and configuring plugins can require technical knowledge, and the interface can feel less intuitive than some newer tools. There can also be configuration issues or failed builds that require troubleshooting. I have limited direct experience with Customer Support, so I cannot strongly evaluate that aspect. > > My overall experience with Jenkins has been positive for development automation and Testing workflows. Its Features provide a high level of flexibility, while Project Management and build tracking capabilities help teams monitor ongoing work. Team Collaboration is useful when multiple developers need visibility into builds and deployment status. Although the Ease of Use could be improved for beginners and configuration can sometimes require troubleshooting, Jenkins provides good Value for Money for teams that need customizable automation. ----- ### "Using Jenkins in managing CI/CD process" — 5.0/5 > **Jim** | *28 de noviembre de 2025* | Telecomunicaciones | Valoración de la recomendación: 10.0/10 > > **Puntos a favor**: Jenkins is super powerful and ease to use in CI/CD, it can integrate all critical phases in checking out, building, testing and delivery. > > **Puntos en contra**: 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. ----- ### "Functional but becomes way too complex" — 3.0/5 > **Edgar** | *22 de diciembre de 2024* | Tecnología y servicios de la información | Valoración de la recomendación: 2.0/10 > > **Puntos a favor**: The software itself is stable, it runs well and is not too complex to install > > **Puntos en contra**: The fact that pipelines are built either with a UI which makes the pipeline tough to read when you have lots of conditions. The groovy language can also be used to write pipelines, but really ?? Let’s use a more common scripting language for this, maybe Python or ruby. ----- ### "A Solid Engineering Workflow Tool That Helps Product Teams" — 5.0/5 > **Braden** | *11 de agosto de 2026* | Diseño | Valoración de la recomendación: 9.0/10 > > **Puntos a favor**: I liked that Jenkins gives product and engineering teams a clear connection between design changes, development, testing, and release. Once the workflow is established, it helps reduce the uncertainty around whether a feature is actually ready to move forward. The automation also means designers don’t have to constantly chase updates from engineering. > > **Puntos en contra**: The interface is probably the weakest part for me. It feels very developer-oriented and can be intimidating if you are coming from a design or product background. Understanding pipelines and configuration also takes some time before it becomes intuitive. > > My experience with Jenkins has been positive, particularly when working closely with engineering teams. It isn't a tool I use to create designs, but it gives me better visibility into how work moves from implementation through testing and release. I found it especially useful on larger projects where several teams needed a consistent process and fewer manual handoffs. ----- ### "The Industry Standard for Flexible, Enterprise-Grade CI/CD Pipelines" — 5.0/5 > **Usuario verificado** | *23 de enero de 2026* | Administración gubernamental | Valoración de la recomendación: 10.0/10 > > **Puntos a favor**: 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. > > **Puntos en contra**: 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. ----- Página: 1 de 24\ Siguiente: [Página siguiente](https://www.capterra.do/software/171026/jenkins?page=2) ## Enlaces - [Ver en Capterra](https://www.capterra.do/software/171026/jenkins) ## Esta página se encuentra disponible en los siguientes idiomas | Local | 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 | | ----- ## Datos estructurados