When comparing CircleCI vs AWS CodeBuild, the Slant community recommends CircleCI for most people. In the question“What are the best hosted continuous integration services?” CircleCI is ranked 1st while AWS CodeBuild is ranked 25th. The most important reason people chose CircleCI is:
CircleCI excels with its setup process. All that's needed is a GitHub login and CircleCI automatically detects the settings for Ruby, Python, Node.js, Java and Clojure. The setup process is their most widely praised feature.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Quick setup
CircleCI excels with its setup process. All that's needed is a GitHub login and CircleCI automatically detects the settings for Ruby, Python, Node.js, Java and Clojure. The setup process is their most widely praised feature.
Pro Simple and intuitive GitHub integration
CircleCI can be connected to any project that is hosted on GitHub by logging in using the GitHub OAuth and adding the desired repository.
Whenever a new commit is pushed to GitHub, CircleCI runs the tests that have been already defined and if none of them fails, the build is deployed to the runtime environment.
Pro SSH support
Users can access the Virtual Machine via SSH and run commands.
Pro Easy configuration with YAML
In most cases CircleCI automatically get settings from your code. When it fails, edit circle.yml.
Pro Very fast parallel testing
Tests can be parallelized across multiple machines reducing test times drastically. They support up to 8-way parallelization. Additionally, CircleCI caches the build environment.
Pro Clean, intuitive UI
Circle CI's web UI is clean and easy to use.
It gives all the information for a single build in a feed and gives the explanation for each step of the build, what it's doing and what the step is related to. On the top it displays author information and the time and date when the build was started and finished.
This is all done by giving only the most essential information without clogging the screen.
Pro Supports 8 languages and 16 databases
Support for Ruby, Python, Node, Java, PHP, RoR, DJ, JavaScript. It also detects settings for Ruby, Python, Node.js, Java and Clojure.
It als has support for: MySQL, MongoDB, PostgreSQL, Cassandra, Riak, Redis, SQLite, Solr, CouchDB, ElasticSearch, Neo4j, Couchbase, Lucene, Sphinx, ThriftDB, Memcache.
Pro Headless browser support
Alongside latest Chrome, Firefox and Webkit (installed using xvfb), CircleCi supports the use of Selenium, PhantomJS as well as tools like Capybara and Cucumber.
Pro Support for Queues
Support for RabbitMQ, Beanstalk and Resque through Redis.
Pro Supports Docker
CircleCI can continuously deliver Docker images to hosts that support Docker containers.
Pro Provides time taken for each step
Eg:
./1.setup.sh 48s
./2.build.sh 56s
With this information, it's easy to find out which line of the script is the bottleneck of the build process.
Pro Comprehensive cache dependencies
Can specify the cache dependencies on
- checksum "package.json"
- Branch
- BuildNum
- Revision
- Environment.variableName
For more details https://circleci.com/docs/2.0/caching/
Pro Intelligent notifications
CircleCI can notify via email, Hipchat, Campfire and more. And it does so only when necessary.
Pro Can test many code pushes concurrently
You can push multiple batches of code concurrently.
Pro Supports 10 Continuous Deployment solutions
Support for Heroku, AWS, Engine Yard, dotCloud, Fabric, Nodejitsu, AppFog, Capistrano, Rockspace, Joynet.
Integration with Heroku is solid with the ability to automatically deploy or merge branches.
CircleCI is also very flexible with the deployment arrangement allowing SSH key management, deployment freedom including directly to a PaaS, using Capistrano, Fabric, arbitrary bash commands, or by auto-merging to another branch, or packaging code up to S3.
Pro Security
Scoped down IAM service roles and managed policies. AWS CloudTrail intergation for API access tracking. AWS Config integration for enforcing complaince rules. Native support for Parameter Store for storing/passing secrets securely to build container.
Pro GitHub cloud, GitHub Enterprise and Bitbucket cloud support
Native support for AWS CodeCommit, S3 and popular git repositories, except GitLab and Bitbucket server.
Pro Compliance
CodeBuild is compliant for PCI, ISO, SOC, and HIPAA workloads.
Pro Documentation and support
Pretty thorough documentation and troubelshooting steps in the CodeBuild user guide @ https://docs.aws.amazon.com/codebuild/latest/userguide/welcome.html.
Questions on the service forum mostly gets prompt response @ https://forums.aws.amazon.com/forum.jspa?forumID=230
Pro Availability
Had minimal to no issues with the service being available. Also, being an AWS service, it has regional endpoint across various AWS regions.
Pro Amazon VPC integration
CodeBuild can access resources within a VPC from it's build containers. Useful for customers who have resources in an Amazon VPC, like RDS instance, ElastiCache, GitHub Enterprise source repo, artifact repo, etc.
Pro On-demand CI. Zero queueing
Users get 20 or so concurrent builds per AWS account ID. Build start up within seconds with no queueing.
Pro Windows support
Support for .NET builds using windowsservercore Docker containers. Preconfigured image have .NET Core and several other runtimes like Java, Node, Ruby. Supports custom images for proprietary tooling like full Visual Studio build targets.
Cons
Con Changes the environment without warning
Unless you count forum posts as a warning. A mysql upgrade caused days of debugging.
Con Does not cache docker images
The way to fake it is to save the image on disk, in the cache folder (it tars it), and restore it afterwards. But in tests it was slower than not caching.
Con Docker is way outdated on the VM provided
Currently (October 5th 2016), Docker installed on the VM is: 1.9.1-circleci-cp-workaround, build 517b158, and docker-compose is 1.5.2, build 7240ff3. docker-compose in particular is almost too old to be used.
Con No iOS support
Limited to Linux and Windows builds.
Con No support for GitLab and Bitbucket server
Off the popular git based source control management system, Bitbucket server and GitLab cloud/on-prem is missing. Generic git support is also not available.
Con No support for Docker layer caching
Customer managed images may be slower for a cold startup than CodeBuild managed ones.
Con No unlimited free builds for Open source repo
CodeBuild gives 100 free mins every month, but no unlimited free builds for Open source repository like Travis CI for example.