AWS CodeBuild vs GitLab CI: What are the differences?
Developers describe AWS CodeBuild as "Build and test code with continuous scaling". AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers. On the other hand, GitLab CI is detailed as "GitLab integrated CI to test, build and deploy your code". GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
AWS CodeBuild and GitLab CI can be primarily classified as "Continuous Integration" tools.
"Pay per minute" is the primary reason why developers consider AWS CodeBuild over the competitors, whereas "Robust CI with awesome Docker support" was stated as the key factor in picking GitLab CI.
WebbyLab, Infoxchange, and Dial Once are some of the popular companies that use GitLab CI, whereas AWS CodeBuild is used by Convox, Volta Industries, and ChromaDex. GitLab CI has a broader approval, being mentioned in 210 company stacks & 93 developers stacks; compared to AWS CodeBuild, which is listed in 21 company stacks and 14 developer stacks.
What is AWS CodeBuild?
What is GitLab CI?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using AWS CodeBuild?
What are the cons of using GitLab CI?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The open-source Convox Platform-as-a-Service is built entirely on AWS cloud services.
Through this lens, it's been obvious that AWS has been missing a managed build service. For the past year we've had to work around this by building our own build service on ECS and ECR. You can read more on my AWS Missing Parts: Build Service blog post.
So I'm excited to finally have this service. After a quick weekend prototype, the service works as expected and will unlock Cheaper, Faster and Safer Builds for our systems.
This is a classic AWS service. It's tricky to figure out all the options. I recommend jumping straight to the Docker example docs:
You'll need to figure IAM, Build Project JSON, and Build Spec YAML to get it all working.
But once you do, you've unlocked managed builds on small, medium or large compute types. No instances required!
We use Gitlab CI to unit and component test all of our application/components/modules. Therefore we use Docker runners.
GitLab CI is extremely flexible and easy to use. We also enjoy the elastic build infrastructure which is Docker based.