Appveyor vs Github Actions

Overview

Appveyor

Stacks123

Followers131

Votes94

GitHub Actions

Stacks48.2K

Followers3.1K

Votes27

Appveyor vs Github Actions: What are the differences?

Key Differences Between Appveyor and Github Actions

Integration with Platform: Appveyor is a Continuous Integration and Deployment (CI/CD) platform that is primarily designed for Windows platforms, whereas Github Actions is a CI/CD tool integrated within the Github ecosystem, providing support for multiple platforms including Windows, MacOS, and Linux.
Supported Workflows: Appveyor is tailored specifically for building, testing, and deploying Windows-based applications, making it ideal for projects targeting the Windows platform. On the other hand, Github Actions offers a wider range of workflow possibilities, allowing developers to automate various tasks, including building, testing, and deploying applications on multiple platforms.
Ease of Use: Github Actions leverages the familiar ecosystem and interface of Github, making it easy for developers already using Github for version control to adopt and configure their workflows. Appveyor has its own separate web interface, which may require additional effort to learn and set up.
Configuration: Github Actions uses YAML-based configuration files to define workflows, giving developers fine-grained control over every aspect of their CI/CD pipelines. Appveyor also supports YAML-based configuration but also provides a web UI for configuration purposes, providing a more visual approach to defining and modifying workflows.
Integration with Version Control: Github Actions is deeply integrated with Github, allowing developers to easily trigger workflows in response to events such as code pushes, pull requests, and issue comments. Appveyor, although supporting integration with Git repositories, may require additional setup and configuration to achieve the same level of integration.
Community and Ecosystem: Github Actions benefits from being part of the Github community, which is rich in terms of resources, community contributions, and available actions shared by other users. Appveyor, while having its own community and resources, may have a smaller user base and a more specific focus on Windows-based projects.

In Summary, Appveyor is a Windows-centric CI/CD platform with a standalone web interface, while Github Actions is a more versatile, platform-agnostic CI/CD tool tightly integrated within the Github ecosystem, supporting multiple platforms and leveraging YAML-based configuration.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Appveyor, GitHub Actions

Somnath

Engineering Leader at Altimetrik Corp.

Jun 25, 2020

Needs adviceon

CircleCI

Drone.io

GitHub Actions

I am in the process of evaluating CircleCI, Drone.io, and GitHub Actions to cover my #CI/ #CD needs. I would appreciate your advice on comparative study w.r.t. attributes like language-Inclusive support, code-base integration, performance, cost, maintenance, support, ease of use, ability to deal with big projects, etc. based on actual industry experience.

Thanks in advance!

1.82M views1.82M

Comments

Detailed Comparison

Appveyor	GitHub Actions
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.	It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
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;	Multiple workflow files support; Free and open source; Workflow run interface; Search for actions in GitHub Marketplace; Integrated with Github's Checks API; Logs and artifacts downloading support
Statistics
Stacks 123	Stacks 48.2K
Followers 131	Followers 3.1K
Votes 94	Votes 27
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 8 Integration with GitHub 5 Free 3 Easy to duplicate a workflow 3 Ready actions in Marketplace 2 Read actions in Marketplace Cons 5 Lacking [skip ci] 4 Lacking allow failure 3 Lacking job specific badges 2 No ssh login to servers 1 No manual launch
Integrations
GitHub Bitbucket .NET	GitHub

What are some alternatives to Appveyor, GitHub Actions?

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.

Airflow

Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command lines utilities makes performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress and troubleshoot issues when needed.

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.

Related Comparisons

Appveyor vs Github Actions: What are the differences?

Key Differences Between Appveyor and Github Actions

Integration with Platform: Appveyor is a Continuous Integration and Deployment (CI/CD) platform that is primarily designed for Windows platforms, whereas Github Actions is a CI/CD tool integrated within the Github ecosystem, providing support for multiple platforms including Windows, MacOS, and Linux.
Supported Workflows: Appveyor is tailored specifically for building, testing, and deploying Windows-based applications, making it ideal for projects targeting the Windows platform. On the other hand, Github Actions offers a wider range of workflow possibilities, allowing developers to automate various tasks, including building, testing, and deploying applications on multiple platforms.
Ease of Use: Github Actions leverages the familiar ecosystem and interface of Github, making it easy for developers already using Github for version control to adopt and configure their workflows. Appveyor has its own separate web interface, which may require additional effort to learn and set up.
Configuration: Github Actions uses YAML-based configuration files to define workflows, giving developers fine-grained control over every aspect of their CI/CD pipelines. Appveyor also supports YAML-based configuration but also provides a web UI for configuration purposes, providing a more visual approach to defining and modifying workflows.
Integration with Version Control: Github Actions is deeply integrated with Github, allowing developers to easily trigger workflows in response to events such as code pushes, pull requests, and issue comments. Appveyor, although supporting integration with Git repositories, may require additional setup and configuration to achieve the same level of integration.
Community and Ecosystem: Github Actions benefits from being part of the Github community, which is rich in terms of resources, community contributions, and available actions shared by other users. Appveyor, while having its own community and resources, may have a smaller user base and a more specific focus on Windows-based projects.

Appveyor vs Github Actions

Overview

Appveyor vs Github Actions: What are the differences?