CircleCI vs Travis CI

• Multiple builds can be run at the same time in parallel.
• The CircleCI web interface (UI/UX) is very easy to understand and use.
• Easy Configuration to learn and use. Just a single configuration YAML file.
• Many integrations. We use the GItHub, Slack, and DataDog integrations.

Read full review

• It is very simple to configure a range of environment versions and settings in a simple YAML file.
• It integrates very well with Github, Bitbucket, or a private Git repo.
• The Travis CI portal beautifully shows you your history and console logs. Everything is presented in a very clear and intuitive interface.

Read full review

• The "phases" their config file uses to separate out options seem very arbitrary and are not very helpful for organizing your config file
• No way that I know of to configure which version of MongoDB you use. You have to write your own shell script to download and start MongoDB if you want a specific version.
• Hard to access build artifacts in the UI

Read full review

• I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
• There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.

Read full review

• It has eased the burden of standardizing our testing and deployment, making onboarding new developers much faster, and having to fix deployment mistakes much less often.
• It allows us to focus our process around the GitHub workflow, ignoring the details of whatever environment the thing we're working on is actually hosted in. This saves us time.

Read full review

• It's improved my ability to deliver working code, increasing my development velocity.
• It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage.
• It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build).
• It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high).
• The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch".

Read full review