Compare CircleCI and Travis CI 
- Users report that CircleCI offers a robust Pipeline Control feature, scoring 8.8, which allows for detailed management of CI/CD processes, while Travis CI excels in Processes and Workflow with a score of 9.6, making it easier for teams to visualize and manage their workflows.
- Reviewers mention that CircleCI's Automation capabilities are rated at 8.8, providing solid automation features, but Travis CI shines with a higher score of 9.8, indicating a more seamless experience in automating deployment processes.
- G2 users highlight that CircleCI's Integration score of 8.5 is decent, but Travis CI stands out with a score of 9.2, showcasing its superior ability to integrate with various third-party tools and services, which is crucial for modern development workflows.
- Users on G2 report that CircleCI's Test Customization feature, rated at 8.2, offers some flexibility, but Travis CI's score of 9.0 indicates a more user-friendly approach to customizing tests, which is essential for tailored CI/CD pipelines.
- Reviewers mention that CircleCI's Quality of Support is rated at 8.1, which is satisfactory, but Travis CI's score of 8.3 suggests a slightly better support experience, with users appreciating quicker response times and more helpful resources.
- Users say that while CircleCI has a solid Deployment-Ready Staging score of 8.7, Travis CI's score of 8.8 indicates a more refined staging process, allowing for smoother transitions from development to production environments.
- 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
- Up to 13,000 build minutes per user/per month
- Unlimited repositories
- Unlimited collaborators
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...
Travis CI is a real life-saver if you need to test your application against different environments. You can test against different language runtimes, different web browsers, different web servers, you name it. The best part of this is you can mix and match...
When too many folks are committing at the same time, it becomes very slow, it struggles during heavy traffic.
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...
Travis CI is a real life-saver if you need to test your application against different environments. You can test against different language runtimes, different web browsers, different web servers, you name it. The best part of this is you can mix and match...
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...
When too many folks are committing at the same time, it becomes very slow, it struggles during heavy traffic.
