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

GitLab CI

1.9K
1.3K
+ 1
71
Netlify

2.2K
1.7K
+ 1
195
Add tool

GitLab CI vs Netlify: What are the differences?

What is GitLab CI? 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.

What is Netlify? Build, deploy and host your static site or app with a drag and drop interface and automatic delpoys from GitHub or Bitbucket. Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment.

GitLab CI and Netlify are primarily classified as "Continuous Integration" and "Static Web Hosting" tools respectively.

"Robust CI with awesome Docker support" is the primary reason why developers consider GitLab CI over the competitors, whereas "Fastest static hosting and continuous deployments" was stated as the key factor in picking Netlify.

According to the StackShare community, GitLab CI has a broader approval, being mentioned in 210 company stacks & 95 developers stacks; compared to Netlify, which is listed in 85 company stacks and 104 developer stacks.

Advice on GitLab CI and Netlify
Needs advice
on
Jenkins X
GitLab CI
and
CircleCI

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
Buildkite

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
jFrog

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 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 GitLab CI and Netlify
Howie Zhao
Full Stack Engineer at yintrust | 7 upvotes 路 114.3K views

We use Netlify to host static websites.

The reasons for choosing Netlify over GitHub Pages are as follows:

  • Netfily can bind multiple domain names, while GitHub Pages can only bind one domain name
  • With Netfily, the original repository can be private, while GitHub Pages free tier requires the original repository to be public

In addition, in order to use CDN, we use Netlify DNS.

See more

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 Private StackShare. Sign up for Private StackShare.
Learn More
Pros of GitLab CI
Pros of Netlify
  • 22
    Robust CI with awesome Docker support
  • 12
    Simple configuration
  • 8
    All in one solution
  • 6
    Source Control and CI in one place
  • 5
    Easy to configure own build server i.e. GitLab-Runner
  • 5
    Integrated with VCS on commit
  • 4
    Free and open source
  • 2
    Hosted internally
  • 1
    Pipeline could be started manually
  • 1
    Built-in support of Review Apps
  • 1
    Enable or disable pipeline by using env variables
  • 1
    Gitlab templates could be shared across logical group
  • 1
    Easy to setup the dedicated runner to particular job
  • 1
    Built-in Docker Registry
  • 1
    Built-in support of Kubernetes
  • 43
    Easy deploy
  • 41
    Fastest static hosting and continuous deployments
  • 21
    Free SSL support
  • 21
    Super simple deploys
  • 15
    Easy Setup and Continous deployments
  • 9
    Free plan for personal websites
  • 9
    Faster than any other option in the market
  • 7
    Deploy previews
  • 6
    Free Open Source (Pro) plan
  • 4
    Easy to use and great support
  • 4
    Analytics
  • 4
    Great loop-in material on a blog
  • 3
    Great drag and drop functionality
  • 3
    Fastest static hosting and continuous deployments
  • 2
    Custom domains support
  • 1
    Canary Releases (Split Tests)
  • 1
    Tech oriented support
  • 1
    Supports static site generators

Sign up to add or upvote prosMake informed product decisions

Cons of GitLab CI
Cons of Netlify
  • 1
    Works best with GitLab repositories
  • 8
    It's expensive
  • 1
    Bandwidth limitation

Sign up to add or upvote consMake informed product decisions

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.

What is Netlify?

Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment.

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

What companies use GitLab CI?
What companies use Netlify?
See which teams inside your own company are using GitLab CI or Netlify.
Sign up for Private StackShareLearn More

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

What tools integrate with GitLab CI?
What tools integrate with Netlify?

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

What are some alternatives to GitLab CI and Netlify?
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.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
Travis CI
Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
TeamCity
TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
CircleCI
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
See all alternatives