StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Appveyor vs Jenkins

Appveyor vs Jenkins

OverviewDecisionsComparisonAlternatives

Overview

Jenkins
Jenkins
Stacks59.2K
Followers50.4K
Votes2.2K
GitHub Stars24.6K
Forks9.2K
Appveyor
Appveyor
Stacks123
Followers131
Votes94

Appveyor vs Jenkins: What are the differences?

Key Differences between Appveyor and Jenkins

Appveyor and Jenkins are both popular continuous integration and delivery (CI/CD) tools used in software development. While they serve the same purpose, there are several key differences between the two:

  1. Pricing and Hosting Options: Appveyor is a cloud-based CI/CD platform that offers both free and paid plans. It provides hosted build environments and manages infrastructure for you. On the other hand, Jenkins is open-source and can be self-hosted, giving you more control over the infrastructure but also requiring you to manage and maintain it.

  2. Ease of Setup and Configuration: Appveyor is known for its ease of setup and configuration. It offers a simple user interface and requires minimal configuration to get started. Jenkins, on the other hand, requires more effort to set up and configure. It is highly customizable but can be more complex, especially for beginners.

  3. Plugin Ecosystem: Jenkins has a vast plugin ecosystem with thousands of plugins available, allowing you to extend its functionality and integrate with various tools and services. Appveyor, on the other hand, has a more limited set of built-in integrations and plugins, which may require more manual setup and configuration.

  4. Supported Platforms: Appveyor primarily focuses on building and testing applications on the Windows platform. It provides preconfigured build environments for .NET, Windows, and other Microsoft technologies. Jenkins, on the other hand, is platform-agnostic and supports building and testing applications on various operating systems, including Windows, macOS, and Linux.

  5. Community Support: Jenkins has a large and active community of users and developers who contribute to its development and provide support through forums, documentation, and plugins. Appveyor has a smaller community but still offers support through documentation and email.

  6. User Interface: Appveyor provides a user-friendly web interface with a modern and intuitive design. It offers a streamlined workflow for configuring and managing CI/CD pipelines. Jenkins, on the other hand, has a more traditional and sometimes complex user interface that may require more technical expertise to navigate and manage.

In summary, Appveyor is a cloud-based CI/CD platform with a simpler setup and configuration, primarily focused on the Windows platform, while Jenkins is an open-source, self-hosted tool with a more extensive plugin ecosystem, platform flexibility, and a larger community support.

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)
or
Manual

Advice on Jenkins, Appveyor

Balaramesh
Balaramesh

Apr 20, 2020

Needs adviceonAzure PipelinesAzure Pipelines.NET.NETJenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k
Comments
Pedro Gil
Pedro Gil

Head of Engineering at lengoo GmbH

May 4, 2021

Decided

We replaced Jenkins with Github Actions for all our repositories hosted on Github. GA has two significant benefits for us compared to an external build tool: it's simpler, and it sits at eye level.

Its simplicity and smooth user experience makes it easier for all developers to adopt, giving them more autonomy.

Sitting at eye level means it's completely run and configured right alongside the code, so that it's easier to observe and adjust our builds as we go.

These two benefits have made "the build" less of a system engineer responsibility and more of a developer tool, giving developers more ownership from code to release.

77.6k views77.6k
Comments
StackShare
StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k
Comments

Detailed Comparison

Jenkins
Jenkins
Appveyor
Appveyor

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.

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.

Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support
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
24.6K
GitHub Stars
-
GitHub Forks
9.2K
GitHub Forks
-
Stacks
59.2K
Stacks
123
Followers
50.4K
Followers
131
Votes
2.2K
Votes
94
Pros & Cons
Pros
  • 523
    Hosted internally
  • 469
    Free open source
  • 318
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 211
    Rich set of plugins with good documentation
Cons
  • 13
    Workarounds needed for basic requirements
  • 10
    Groovy with cumbersome syntax
  • 8
    Plugins compatibility issues
  • 7
    Lack of support
  • 7
    Limited abilities with declarative pipelines
Pros
  • 20
    Github integration
  • 18
    Simple, reliable & powerful
  • 12
    Hosted
  • 11
    YML-based configuration
  • 10
    Nuget support
Cons
  • 1
    Complex user interface
  • 1
    Poor documentation
Integrations
No integrations available
GitHub
GitHub
Bitbucket
Bitbucket
.NET
.NET

What are some alternatives to Jenkins, Appveyor?

Travis CI

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

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

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

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

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

GoCD

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

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

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.

Snap CI

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana