Appveyor vs GoCD: What are the differences?
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; GoCD: Open source continuous delivery tool allows for advanced workflow modeling and dependencies management. 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.
Appveyor and GoCD 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, GoCD provides the following key features:
- Model complex workflows with dependency management and parallel execution
- Easy to pass once-built binaries between stages
- Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance
"Github integration" is the primary reason why developers consider Appveyor over the competitors, whereas "Open source" was stated as the key factor in picking GoCD.
GoCD is an open source tool with 5.07K GitHub stars and 796 GitHub forks. Here's a link to GoCD's open source repository on GitHub.
Auto Trader, Hazeorid, and OpenX are some of the popular companies that use GoCD, whereas Appveyor is used by Snipcart, Hangfire, and Exceptionless. GoCD has a broader approval, being mentioned in 40 company stacks & 78 developers stacks; compared to Appveyor, which is listed in 27 company stacks and 70 developer stacks.
What is Appveyor?
What is GoCD?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Appveyor?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I recommend using Travis CI and/or Appveyor in all projects.
Projects using these tools have given me confidence to know that I don't cause any breaking changes. Travis CI and Appveyor have functionality to test components of a project across multiple installation projects to ensure that modifications don't break a project. These tools integrate easily with GitHub and are useful in open source projects that must review contributions from many different people.
Appveyor, is awesome, it provides a lot of functionalities and a reduced price. If you want .NET CI, appveyor is the best option. Ever. Awesome support, easy configuration, private nuget repo included, many integrations, and useful documentation. The only downside is, sometime it's a little bit slow.