Choosing CircleCI versus Travis CI
CircleCI offers the same simplicity as Travis CI, while delivering more powerful and flexible features designed to scale from the smallest projects to the largest enterprises.
Speedy builds for all projects
CircleCI supports open source projects and allocates substantial resources for both paid and free users without affecting queue times. You have the ability to choose the CPU and RAM you need regardless of your project type with various price plans to fit your team’s needs across Linux and iOS projects. Teams building on TravisCI have reported long build queues, inability to adjust resources, and resorting to utilizing local machines just to speed up builds.
Teams gain complete control with workflows
Teams looking to scale and customize their development process can do so with CircleCI. By breaking jobs into functional pieces, teams can decide when and how they’d like to configure their jobs and orchestrate parts of the build. Customizing workflows allows teams to persist artifacts across job stages, filter by branches, and schedule approved jobs.
Increased efficiency with shared control and workspaces
Having control centralized at an org-level is a helpful way to share variables across projects. This frees teams from having to reconfigure environmental variables per project. Though Travis CI offers convenience variables, sharing environment variables across an org isn’t currently supported. CircleCI provides Contexts to secure and share environment variables, and workspaces to persist data, or move it between jobs.
Premium support (custom SLAs, success team)
Whether you’re new to CircleCI or continuing to adopt continuous integration and delivery, your team will get the resources it needs to be successful. When choosing a CI provider, it’s important to select one that will grow with your team. Additionally, all customers can access Live System Status Updates, Ticket-based Global Support, and Community-based Support via Discuss for free.
