Appveyor聽vs聽Jenkins

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

Appveyor

116
114
+ 1
93
Jenkins

36.2K
28.9K
+ 1
2.2K
Add tool

Appveyor vs Jenkins: What are the differences?

What is Appveyor? Continuous Integration and Deployment service for busy Windows developers. 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 Jenkins? An extendable open source continuous integration server. 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 and Jenkins can be primarily classified as "Continuous Integration" tools.

Some of the features offered by Appveyor are:

  • Scriptless, repetitive, one-click deployment of build artifacts to multiple environments
  • YAML configuration
  • Backed by Windows Azure platform

On the other hand, Jenkins provides the following key features:

  • Easy installation
  • Easy configuration
  • Change set support

"Github integration" is the primary reason why developers consider Appveyor over the competitors, whereas "Hosted internally" was stated as the key factor in picking Jenkins.

Jenkins is an open source tool with 13.3K GitHub stars and 5.48K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.

Facebook, Netflix, and Instacart are some of the popular companies that use Jenkins, whereas Appveyor is used by Trustpilot, Snipcart, and Exceptionless. Jenkins has a broader approval, being mentioned in 1774 company stacks & 1526 developers stacks; compared to Appveyor, which is listed in 19 company stacks and 16 developer stacks.

Decisions about Appveyor and Jenkins
Kirill Mikhailov

Jenkins is a friend of mine. 馃榾

There are not much space for Jenkins competitors for now from my point of view. With declarative pipelines now in place, its super easy to maintain them and create new ones(altho I prefer scripted still). Self-hosted, free, huge community makes it the top choice so honestly for me it was an easy pick.

See more
Stephen Badger | Vital Beats
Senior DevOps Engineer at Vital Beats | 2 upvotes 路 38.6K views

Within our deployment pipeline, we have a need to deploy to multiple customer environments, and manage secrets specifically in a way that integrates well with AWS, Kubernetes Secrets, Terraform and our pipelines ourselves.

Jenkins offered us the ability to choose one of a number of credentials/secrets management approaches, and models secrets as a more dynamic concept that GitHub Actions provided.

Additionally, we are operating Jenkins within our development Kubernetes cluster as a kind of system-wide orchestrator, allowing us to use Kubernetes pods as build agents, avoiding the ongoing direct costs associated with GitHub Actions minutes / per-user pricing. Obviously as a consequence we take on the indirect costs of maintain Jenkins itself, patching it, upgrading etc. However our experience with managing Jenkins via Kubernetes and declarative Jenkins configuration has led us to believe that this cost is small, particularly as the majority of actual building and testing is handled inside docker containers and Kubernetes, alleviating the need for less supported plugins that may make Jenkins administration more difficult.

See more

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Pros of Appveyor
Pros of Jenkins
  • 20
    Github integration
  • 18
    Simple, reliable & powerful
  • 11
    Hosted
  • 11
    YML-based configuration
  • 10
    Nuget support
  • 6
    Windows support
  • 4
    Automatic deployment
  • 4
    Free for open source
  • 3
    Great product, responsive people, free for open-source
  • 2
    Easy PowerShell support
  • 2
    Easy handling of secret keys
  • 1
    Advanced build workers available
  • 1
    Remote Desktop into Build Worker
  • 520
    Hosted internally
  • 463
    Free open source
  • 313
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 208
    Rich set of plugins with good documentation
  • 108
    Has support for build pipelines
  • 71
    Open source and tons of integrations
  • 63
    Easy setup
  • 61
    It is open-source
  • 54
    Workflow plugin
  • 11
    Configuration as code
  • 10
    Very powerful tool
  • 9
    Many Plugins
  • 8
    Git and Maven integration is better
  • 8
    Great flexibility
  • 6
    Continuous Integration
  • 6
    Slack Integration (plugin)
  • 6
    Github integration
  • 5
    Easy customisation
  • 5
    Self-hosted GitLab Integration (plugin)
  • 4
    100% free and open source
  • 4
    Docker support
  • 3
    Excellent docker integration
  • 3
    Fast builds
  • 3
    Platform idnependency
  • 2
    Pipeline API
  • 2
    Customizable
  • 2
    Can be run as a Docker container
  • 2
    It`w worked
  • 2
    Hosted Externally
  • 2
    AWS Integration
  • 2
    JOBDSL
  • 2
    It's Everywhere
  • 1
    NodeJS Support
  • 1
    PHP Support
  • 1
    Ruby/Rails Support
  • 1
    Universal controller
  • 1
    Easily extendable with seamless integration
  • 1
    Build PR Branch Only

Sign up to add or upvote prosMake informed product decisions

Cons of Appveyor
Cons of Jenkins
  • 1
    Complex user interface
  • 1
    Poor documentation
  • 12
    Workarounds needed for basic requirements
  • 7
    Groovy with cumbersome syntax
  • 6
    Plugins compatibility issues
  • 6
    Limited abilities with declarative pipelines
  • 5
    Lack of support
  • 4
    No YAML syntax
  • 2
    Too tied to plugins versions

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

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

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

What companies use Appveyor?
What companies use Jenkins?

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

What tools integrate with Appveyor?
What tools integrate with Jenkins?

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

Blog Posts

GitJenkinsGroovy+4
3
1568
Dec 4 2019 at 8:01PM
https://img.stackshare.io/stack/519120/default_d8fbac59cb4c75cc8da7062d0dc1d02daa76fa62.png logo

Pinterest

JenkinsKubernetesTensorFlow+4
5
2795
GitHubPythonGit+22
17
13031
JavaScriptGitHubPython+42
52
19242
What are some alternatives to Appveyor and Jenkins?
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.
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.
Azure Pipelines
Fast builds with parallel jobs and test execution. Use container jobs to create consistent and reliable builds with the exact tools you need. Create new containers with ease and push them to any registry.
See all alternatives
Interest over time
News about Appveyor
More news