Need advice about which tool to choose?Ask the StackShare community!
Appveyor vs wercker: 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 wercker? Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Appveyor and wercker belong to "Continuous Integration" category of the tech stack.
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, wercker provides the following key features:
- Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.
- Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.
- Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.
"Github integration" is the top reason why over 18 developers like Appveyor, while over 34 developers mention "Automatic Deployments" as the leading cause for choosing wercker.
FashionUnited, Hazeorid, and Wantedly are some of the popular companies that use wercker, whereas Appveyor is used by Trustpilot, Snipcart, and Exceptionless. wercker has a broader approval, being mentioned in 40 company stacks & 23 developers stacks; compared to Appveyor, which is listed in 19 company stacks and 16 developer stacks.
We migrated all our CI/CD pipelines to CircleCI back in 2017 and are particularly happy about it since!
Our top loved feature is unlimited parallelism. We can run as many builds concurrently as we want.
We also use orbs, pipeline parameters, reusable commands, build cache, test insights.
For some of the heavier repos, we use a larger resource class and mount RAMdisk to a file system to speed up builds.
Pros of Appveyor
- Github integration20
- Simple, reliable & powerful18
- Hosted12
- YML-based configuration11
- Nuget support10
- Windows support6
- Free for open source4
- Automatic deployment4
- Great product, responsive people, free for open-source3
- Easy PowerShell support2
- Easy handling of secret keys2
- Remote Desktop into Build Worker1
- Advanced build workers available1
Pros of wercker
- Automatic Deployments35
- Free33
- Easy config via yaml25
- Awesome UI23
- Github integration23
- Continuous Deployment22
- Supports both Github and Bitbucket16
- Easy to setup14
- Reliable12
- Bitbucket Integration11
- Community-driven components (boxes and steps)4
- Fast builds4
- Easy to get started4
- Docker based4
- Easy UI3
- Flexible configuration via YAML3
- Multi-target deploys2
- Trigger by branch name1
- Great UI, free and an active Slack channel :)1
- Docker support1
- Multiple configurable build steps1
Sign up to add or upvote prosMake informed product decisions
Cons of Appveyor
- Complex user interface1
- Poor documentation1
