Overview

Appveyor

Stacks123

Followers131

Votes94

GitLab CI

Stacks2.3K

Followers1.6K

Votes75

GitHub Stars0

Forks0

Appveyor vs GitLab CI: What are the differences?

Key Differences between Appveyor and GitLab CI

Appveyor and GitLab CI are two popular continuous integration (CI) platforms used for automating the build, test, and deployment processes. While they both serve the same purpose, there are several key differences between the two.

Hosted vs self-hosted: Appveyor is a fully hosted CI platform, which means it provides a ready-to-use infrastructure for running your CI pipelines. On the other hand, GitLab CI can be self-hosted, allowing you to have full control over the CI environment and infrastructure.
Integrated vs standalone: GitLab CI is part of the larger GitLab platform, which includes features such as source code management, issue tracking, and collaboration tools. This integration allows for seamless integration between code management and CI. Appveyor, however, is a standalone CI platform and does not offer other features beyond the CI capabilities.
Operating system support: Appveyor primarily focuses on providing CI services for Windows-based projects. It offers extensive support for various versions of Windows, including older ones. GitLab CI, on the other hand, supports a wider range of operating systems, including Windows, MacOS, and Linux.
Configuration language: Appveyor uses a YAML-based configuration language for defining CI pipelines. It allows for a simple and straightforward syntax, making it easier for developers to define their build and deployment steps. GitLab CI also uses YAML for configuration, but it provides a more versatile and powerful syntax, allowing for more complex and flexible pipeline definitions.
Extensibility and integrations: GitLab CI provides a rich ecosystem of plugins and integrations, allowing for seamless integration with various external tools and services. This includes integrations with popular code quality analysis tools, monitoring platforms, and deployment services. Appveyor also supports some integrations but has a more limited set compared to GitLab CI.
Visibility and collaboration: GitLab CI provides a robust set of features for collaboration and visibility. It allows for multiple users and teams to collaborate on CI pipelines, define roles and permissions, and provides a centralized dashboard for monitoring and managing pipelines. Appveyor also provides some collaboration features but lacks the level of visibility and collaboration capabilities offered by GitLab CI.

In summary, Appveyor and GitLab CI differ in terms of hosting options, integration with other tools, operating system support, configuration language, extensibility, and collaboration features. Choosing between the two depends on specific project requirements, preferred hosting options, and the need for integration with other tools or features beyond CI.

🔥 Trending in Continuous Integration on StackShare

GitHub Actions Continuous Integration

Automate your workflow from idea to production

Try it View Docs Alternatives

Try

4.23k

3.11k

Advice on Appveyor, GitLab CI

Stratos

Jan 13, 2020

Needs advice

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

181k views181k

Comments

Anonymous

Feb 14, 2020

Decided

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:

Add repo
Click - Click - Click
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.

157k views157k

Comments

Detailed Comparison

Appveyor	GitLab CI
AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.	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.
Scriptless, repetitive, one-click deployment of build artifacts to multiple environments;YAML configuration;Backed by Windows Azure platform;Built-in NuGet feeds with project artifacts;Build artifacts are stored in a highly-durable Geo-redundant cloud storage;	-
Statistics
GitHub Stars -	GitHub Stars 0
GitHub Forks -	GitHub Forks 0
Stacks 123	Stacks 2.3K
Followers 131	Followers 1.6K
Votes 94	Votes 75
Pros & Cons
Pros 20 Github integration 18 Simple, reliable & powerful 12 Hosted 11 YML-based configuration 10 Nuget support Cons 1 Poor documentation 1 Complex user interface	Pros 22 Robust CI with awesome Docker support 13 Simple configuration 9 All in one solution 7 Source Control and CI in one place 5 Easy to configure own build server i.e. GitLab-Runner Cons 2 Works best with GitLab repositories
Integrations
GitHub Bitbucket .NET	GitLab

What are some alternatives to Appveyor, 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.

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.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

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.

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.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.