Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing CloudBees vs AppVeyor, the Slant community recommends CloudBees for most people. In the question“What are the best hosted continuous integration services?” CloudBees is ranked 8th while AppVeyor is ranked 17th. The most important reason people chose CloudBees is:
Quick access to experts who are responsive, helpful, and friendly.
Specs
Question Ranking
Pros
Pro Great enterprise level support
Quick access to experts who are responsive, helpful, and friendly.
Pro Private and internal SVN and Git repositories
Support for both SVN and Git private repositories.
Pro Highly customisable
Jenkins is by far the most customizable solution on the market. And CloudBees is built on Jenkins. There are over 400 plugins to support building and testing virtually any project.
Pro Free for open source projects
CloudBees offers a solution for owners and developers of free and open source projects to be hosted and built by their service.
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.
Cons
Con Java-only solution (without plugins)
Jenkins supports only software built with Java (unless you use plugins)
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.
