Compare CircleCI and Jenkins 
- Users report that CircleCI excels in automation with a score of 8.9, while Jenkins shines even brighter with a score of 9.3, indicating Jenkins may offer more robust automation features that users find beneficial for their CI/CD processes.
- Reviewers mention that CircleCI's integration capabilities are strong, scoring 8.5, but Jenkins outperforms with a score of 8.8, suggesting that Jenkins provides a wider range of integrations that users appreciate for connecting various tools and services.
- G2 users highlight CircleCI's ease of setup with a score of 8.4, which is notably higher than Jenkins' score of 7.8, indicating that users find CircleCI more user-friendly when it comes to initial configuration and deployment.
- Reviewers say that CircleCI's reporting features score 7.7, which is lower than Jenkins' score of 8.2, suggesting that Jenkins may offer more comprehensive reporting tools that help users track their CI/CD performance more effectively.
- Users on G2 report that CircleCI's extensibility is rated at 8.0, while Jenkins scores higher at 8.6, indicating that Jenkins may provide more options for customization and extending functionality, which is crucial for teams with specific needs.
- Users say that both products have similar scores for pipeline control, with CircleCI at 8.8 and Jenkins at 8.9, but Jenkins' slight edge suggests it may offer more refined controls for managing complex pipelines, which is a key feature for many development teams.
- Up to 6,000 build minutes per month
- Largest selection: Build for Docker, Windows, Linux, Arm, and macOS or on your own compute with self-hosted runners
- Build better: Choose the right resource class size (S–L) to go fast and maximize your build minutes
Things that I like arranged sorted by usefulness - 1. * Debug via SSH * - This is pretty much the best feature it has, where you can actively debug your builds when there is a error instead of just failing. As the tests are run on their containers, it...
Occasional connectivity issues, nonsense 137 OOM and infrastructure failure which result in build failures with no part on our end. That costs us credits. 137 OOM error happens from time to time to our Node.JS application when their dashboard resources show...
Jenkins is the best Open Source Pipeline Tool For CI/CD pipelines. Using Jenkins It's Enhance the Product Life Cycle with the Power of Automation. We are using Jenkins to perform part of our deployment pipeline, All the Code and tests are performed through...
Markup. All the configuration is stored in XML, which imho is overkill for what Jenkins does. It also makes version control awkward. I really wish I could use git to keep track of versions of jobs and also as deployment method. Linux sys admins tend to live...
Things that I like arranged sorted by usefulness - 1. * Debug via SSH * - This is pretty much the best feature it has, where you can actively debug your builds when there is a error instead of just failing. As the tests are run on their containers, it...
Jenkins is the best Open Source Pipeline Tool For CI/CD pipelines. Using Jenkins It's Enhance the Product Life Cycle with the Power of Automation. We are using Jenkins to perform part of our deployment pipeline, All the Code and tests are performed through...
Occasional connectivity issues, nonsense 137 OOM and infrastructure failure which result in build failures with no part on our end. That costs us credits. 137 OOM error happens from time to time to our Node.JS application when their dashboard resources show...
Markup. All the configuration is stored in XML, which imho is overkill for what Jenkins does. It also makes version control awkward. I really wish I could use git to keep track of versions of jobs and also as deployment method. Linux sys admins tend to live...
