Need advice about which tool to choose?Ask the StackShare community!

AWS CodeBuild

413
421
+ 1
43
GitLab CI

2.1K
1.4K
+ 1
72
Add tool

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鈥檛 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.

Advice on AWS CodeBuild and GitLab CI
Needs advice
on
CircleCICircleCIGitLab CIGitLab CI
and
Jenkins XJenkins X

We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.

Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.

We primarily need:

  • Fast SBT builds (caching)
  • Low maintenance overhead (ideally serverless)
  • Everything as code
  • Ease of use
See more
Replies (3)
Glenn Gillen
Recommends
BuildkiteBuildkite

I think I've tried most of the CI tools out there at some point. It took me a while to get around to Buildkite because at first I didn't see much point given it seemed like you had to run the agent yourself. Eventually it dawned on me why this approach was more ingenious than I realised:

Running my app in a production (or production-like) environment was already a solved problem, because everything was already in some form of "everything as code". Having a test environment where the only difference was adding the Buildkite agent was a trivial addition.

It means that dev/test/prod parity is simple to achieve and maintain. It's also proven to be much easier to support than trying to deal with the problems that come with trying to force an app to fit into the nuances and constraints that are imposed by the containers/runtime of a CI service. When you completely control all of the environment the tests are running in you define those constraints too. It's been a great balance between a managed service and the flexibility of running it yourself.

And while none of my needs have hit the scale of Shopify (I saw one of their engineers speak about it at a conference once, I can't find the video now though 馃槥) it's good to know I can scale out my worker nodes to hundreds of thousands of workers to reduce the time it takes for my tests to run.

See more
Recommends
jFrogjFrog

I would recommend you to consider the JFrog Platform that includes JFrog Pipelines - it will allow you to manage the full artifact life cycle for your sbt, docker and other technologies, and automate all of your CI and CD using cloud native declarative yaml pipelines. Will integrate smoothly with all your other toolset.

See more
Estu Fardani
Recommends
GitLab CIGitLab CI

more configurable to setup ci/cd: * It can provide caching when build sbt, just add this section to yml file * Easy to use, many documentation

Weakness: * Need use gitlab as repository to bring more powerful configuration

See more
Decisions about AWS CodeBuild and GitLab CI

Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like: 1. Add repo 2. Click - Click - Click 3. You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS CodeBuild
Pros of GitLab CI
  • 7
    Pay per minute
  • 5
    Parameter Store integration for passing secrets
  • 4
    Integrated with AWS
  • 3
    Bit bucket integration
  • 3
    Streaming logs to Amazon CloudWatch
  • 2
    AWS Config and Config rule integration for compliance
  • 2
    GitHub Webhooks support
  • 2
    VPC PrivateLinks to invoke service without internet
  • 1
    Windows/.NET support
  • 1
    Jenkins plugin integration
  • 1
    Ondemand scaling of build jobs
  • 1
    Scheduled builds with CloudWatch Events integration
  • 1
    Local build debug support
  • 1
    Native support for accessing Amazon VPC resources
  • 1
    Docker based build environment
  • 1
    Support for bringing custom Docker images
  • 1
    Fully managed (no installation/updates, servers to mai
  • 1
    PCI, SOC, ISO, HIPAA compliant
  • 1
    Full API/SDKs/CLI support
  • 1
    YAML based configuration
  • 1
    Great support (forums, premium support, SO, GitHub)
  • 1
    Perpetual free tier option (100 mins/month)
  • 1
    GitHub Enterprise support
  • 22
    Robust CI with awesome Docker support
  • 12
    Simple configuration
  • 8
    All in one solution
  • 6
    Source Control and CI in one place
  • 5
    Integrated with VCS on commit
  • 5
    Easy to configure own build server i.e. GitLab-Runner
  • 5
    Free and open source
  • 2
    Hosted internally
  • 1
    Built-in support of Kubernetes
  • 1
    Easy to setup the dedicated runner to particular job
  • 1
    Enable or disable pipeline by using env variables
  • 1
    Gitlab templates could be shared across logical group
  • 1
    Built-in Docker Registry
  • 1
    Pipeline could be started manually
  • 1
    Built-in support of Review Apps

Sign up to add or upvote prosMake informed product decisions

Cons of AWS CodeBuild
Cons of GitLab CI
  • 1
    Poor branch support
  • 2
    Works best with GitLab repositories

Sign up to add or upvote consMake informed product decisions

What is AWS CodeBuild?

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鈥檛 need to provision, manage, and scale your own build servers.

What is GitLab CI?

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.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention AWS CodeBuild and GitLab CI as a desired skillset
CBRE
United States of America Texas Richardson
CBRE
United States of America Texas Boston
CBRE
Poland Mazowieckie Warsaw
CBRE
United States of America Texas Dallas
What companies use AWS CodeBuild?
What companies use GitLab CI?
See which teams inside your own company are using AWS CodeBuild or GitLab CI.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with AWS CodeBuild?
What tools integrate with GitLab CI?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to AWS CodeBuild and GitLab CI?
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
AWS CodePipeline
CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
Apache Maven
Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
AWS CodeDeploy
AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications.
AWS CodeStar
Start new software projects on AWS in minutes using templates for web applications, web services and more.
See all alternatives