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

Appveyor

124
130
+ 1
94
GitHub Actions

22K
2.4K
+ 1
27
Add tool

Appveyor vs Github Actions: What are the differences?

Key Differences Between Appveyor and Github Actions

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Appveyor
Pros of GitHub Actions
  • 20
    Github integration
  • 18
    Simple, reliable & powerful
  • 12
    Hosted
  • 11
    YML-based configuration
  • 10
    Nuget support
  • 6
    Windows support
  • 4
    Free for open source
  • 4
    Automatic deployment
  • 3
    Great product, responsive people, free for open-source
  • 2
    Easy PowerShell support
  • 2
    Easy handling of secret keys
  • 1
    Remote Desktop into Build Worker
  • 1
    Advanced build workers available
  • 8
    Integration with GitHub
  • 5
    Free
  • 3
    Easy to duplicate a workflow
  • 3
    Ready actions in Marketplace
  • 2
    Configs stored in .github
  • 2
    Docker Support
  • 2
    Read actions in Marketplace
  • 1
    Active Development Roadmap
  • 1
    Fast

Sign up to add or upvote prosMake informed product decisions

Cons of Appveyor
Cons of GitHub Actions
  • 1
    Complex user interface
  • 1
    Poor documentation
  • 5
    Lacking [skip ci]
  • 4
    Lacking allow failure
  • 3
    Lacking job specific badges
  • 2
    No ssh login to servers
  • 1
    No Deployment Projects
  • 1
    No manual launch

Sign up to add or upvote consMake informed product decisions

What is Appveyor?

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.

What is GitHub Actions?

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.

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

Jobs that mention Appveyor and GitHub Actions as a desired skillset
What companies use Appveyor?
What companies use GitHub Actions?
See which teams inside your own company are using Appveyor or GitHub Actions.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Appveyor?
What tools integrate with GitHub Actions?

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

What are some alternatives to Appveyor and GitHub Actions?
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.
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.
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.
Azure DevOps
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
See all alternatives