Compare CircleCI and Travis CI 
- Users report that CircleCI offers a more flexible configuration management system, allowing for easier customization of pipelines, while Travis CI's configuration is often seen as more straightforward but less flexible.
- Reviewers mention that CircleCI excels in automation capabilities, particularly with its "Workflows" feature, which allows for complex job orchestration, whereas Travis CI's automation is effective but can be less intuitive for intricate setups.
- G2 users highlight that Travis CI has superior integration options, particularly with GitHub, making it easier to set up continuous integration for projects hosted there, while CircleCI is praised for its extensive support for various languages and frameworks.
- Users on G2 say that CircleCI's reporting features, while functional, do not provide as much depth as those in Travis CI, which offers more detailed insights into build performance and history.
- Reviewers mention that CircleCI's extensibility is a strong point, allowing users to create custom Docker images, while Travis CI's extensibility is more limited, which can hinder advanced users looking for tailored solutions.
- Users say that the overall ease of setup is slightly better in Travis CI, with many finding it quicker to get started, while CircleCI may require a steeper learning curve due to its more complex features.
- 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 keeps check on all my builds, running the tests it's configured to run. Travis CI not only runs tests on your master developing branch, it may also be configured to test all your feature branches and even Pull Requests, which an amazing feature as...
The real downside of Travis is that you need to add a file to your project to start using it. This is mandatory today and this file can be quite complex. This leads to some "useless" commits just to correct some configuration in this file and check if it...
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 keeps check on all my builds, running the tests it's configured to run. Travis CI not only runs tests on your master developing branch, it may also be configured to test all your feature branches and even Pull Requests, which an amazing feature as...
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...
The real downside of Travis is that you need to add a file to your project to start using it. This is mandatory today and this file can be quite complex. This leads to some "useless" commits just to correct some configuration in this file and check if it...