AppVeyorhttps://www.appveyor.com |
Shippablehttps://www.shippable.com |
|
---|---|---|
Unique feature |
Supports NuGet packages / Windows build environment
|
N/A
|
Type of product |
SaaS / On Premise
|
SaaS / On Premise
|
Offers a free plan |
Yes Free SaaS plan for open source projects. There is also a free on premise version, but it's quite limited (1 user, 1 team, community support) |
Yes Free unlimited builds for open source projects, 150 builds per month for all others (hosted plan). For the on-premise solution they only offer a 30 day trial. |
Predictable pricing |
Yes Very simple pricing plans: 3 options for the SaaS version, two options for the on premise option. No variable pricing. |
Yes Clear pricing based on number of concurrent jobs. They also allow a varied combination of platforms you want to run (Ubuntu, Windows, MacOS, CentOS) and provide a Bring Your Own Node option (so you can run builds on your own infrastructure) |
Support / SLA |
Yes All paid on premise plans offer support, as well as the two higher priced SaaS plans. Only community support available for the free on premise version and the lowest SaaS tier. |
Yes One of the few competitors to offer support tiers with clearly defined SLAs: https://www.shippable.com/premium-support.html as well as Services and Training: https://www.shippable.com/devops-services.html |
Paralellism
Every CI servers tends to address this differently (parallel, distributed, build matrix). Some of it is just marketing, and some is just nuance. For this table, parallel means that tasks can be run concurrently on the same machine, distributed means that tasks can be scaled horizontally, on multiple machines How to split tests in parallel in the optimal way with Knapsack Pro |
Yes Allows splitting tests to run on different VMs in parallel. |
Yes One thing that stands out, is the shipctl CLI tool, which can automatically determine which tests to run in parallel, based on previous performance, such that a minimal amount of time is ensured: http://docs.shippable.com/ci/running-parallel-tests/#running-tests-in-parallel |
Distributed builds
distributed means that tasks can be scaled horizontally, on multiple machines How to split tests in parallel in the optimal way with Knapsack Pro |
N/A
|
N/A No specific mention. From the wording, multiple environments are certainly available, but it's unclear if the tasks can be distributed to multiple containers/VMs on the same machine, or multiple machines. |
Containers support / Build environment |
Yes Runs every build in a VM, and it offers several options depending on the plan (SaaS or self-hosted) as well sa personal preference. |
Yes Native Docker support |
Analytics / Status overview
Analytics and overview referrs to the ability to, at a glance, see what's breaking (be it a certain task, or the build for a specific project) |
Yes The dashboard is not as great as for other options in the market, but allows seeing project status at a glance. |
Yes Detailed statistics available at multiple levels (job, account, project, etc.). They also include a view they call SPOG (Single Pane of Glass) which allows viewing a real-time representation of all of the pipelines in the organization, from where you can drill-in to the leaf nodes you're interested in. |
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes Allows creating teams and assigning roles. There is some integration with GitHub Teams but the concepts are different which might be tricky depending on how the GitHub project is managed, for instance. |
Yes
|
Self-hosted option |
Yes
|
Yes
|
Hosted plans / SaaS |
Yes
|
Yes
|
Build pipelines
A continuous delivery pipeline is a description of the process that the software goes through from a new code commit, through testing and other statical analysis steps all the way to the end-users of the product. |
Yes There is a single predefined possible pipeline, which defines various hooks (such as before_build / after_build). The pipeline can be configured via the UI or via an appveyor.yml file. The two are mutually exclusive, so it's either one or the other. |
Yes Configurable via an YML file (called Assembly Lines) |
Reports
Reports are about the abilty to see specific reports (like code coverage or custom ones), but not necesarily tied in into a larger dashboard. |
Yes Notifications are highly configurable, but visual reports such as code coverage is not easy to implement. |
Yes
|
Ecosystem
Besides the official documentation and software, is there a large community using this product? Are there any community-driven tools / plugins that you can use? |
N/A
|
Yes https://www.shippable.com/integrations.html |
Specific language support: Ruby
Some CI servers have built-in support for parsing RSpec or Istanbul output for example and we mention those. Some others make it even easier by detecting Gemfiles or package.json and automate parts of the process for the developer. |
Yes Many Ruby gems use AppVeyor as their CI server of choice. Among the features for Ruby are the pre-installed Ruby versions on both Windows and Ubuntu servers, as well as the appveyor-worker gem which makes it easy to report status during the build process. |
Yes Ruby is available by default on the Shippable container images. They also provide support for tools such as Cucumber or RSpec. Specific documentation for Ruby available on the website: http://docs.shippable.com/ci/ruby-continuous-integration/ |
Specific language support: JavaScript |
Yes Comes with node.js and io.js versions pre-installed. Also offers documentation on npm integration on their website. |
Yes Specific documentation for Node.js available: http://docs.shippable.com/ci/ruby-continuous-integration/ |
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Probably the most notable aspect here is the large array of deployment integrations available (from simple FTP uploads to Azure servers or NuGet packages). |
Yes http://docs.shippable.com/ci/ruby-continuous-integration/ |
API
Custom integreation is available, via an API or otherwise, it's mentioned separately as it allows further customization than any of the Ecosystem/Integration options |
Yes Offers a basic CRUD REST API for querying projects and builds as well as a real-time Build Worker API which can send updates on build status. |
Yes Provides a straight-forward REST API: http://docs.shippable.com/platform/api/api-overview/. They also provide ways to integrate notifications in your workflow, via webhooks or specific channels (IRC, Slack, Email, etc): http://docs.shippable.com/ci/send-notifications/ |
Auditing |
N/A
|
Yes
|
Additional notes |
Very Windows oriented |
|