Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing AppVeyor vs GoCD, the Slant community recommends AppVeyor for most people. In the question“What are the best continuous integration tools?” AppVeyor is ranked 4th while GoCD is ranked 18th. The most important reason people chose AppVeyor is:
AppVeyor is free for public GitHub repositories.
Specs
Question Ranking
Pros
Pro Free for open-source projects
AppVeyor is free for public GitHub repositories.
Pro Supports Windows build enviroment
AppVeyor has a build environment for Windows available.
Pro Clear, straight-forward user interface
Well I suggest you check it out for yourself, but what I like most is that it's simple yet effective: no bells and whistles, simple black/grey/light-blue/white color scheme, it's immediately clear where you have to go for each specific task, and build settings pages are like that as well. Getting a 'standard' build running literally took me a minute the first time I used it.
Pro Easy access to build VM
AppVeyor allows the user to login to the actual build VM.
Pro The initial setup is easy
There's practically no setup involved prior to working with AppVeyor: simply sign in, add the project, and start a new build.
Pro Native support for pipelines
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Pro Good traceability of what contributed to a given artifact
GoCD's LEAN value stream UI helps all stakeholders focus on efficient product delivery (instead of collections of technical tasks).
Cons
Con Not free
This is open-source but not free.
Con Configuration is limited
AppVeyor's configuration (which is done from the .yaml file in the root of the project) is unfortunately very limited. The configuration is either tied to a branch or, in other cases, it's global. This limits the developer to a single build process.
However, since you can use arbitrary scripts for building, all those limitations can be overcome. Configuration can also be done from the web UI without a .yaml file.
Con Need Scripts for everything
Almost all operations are shell based, they are not configurations possible, your CI is as good as your scripting
Con Does not offer many plugins
Since it's relatively new and not very popular, there are few plugins available in GoCD.
Con Somewhat tricky to setup
