AppVeyor Reviews

Unlike other C.I tools that are built in a linux environment, appveyor is built in a windows environment which allows you to test application performance in windows. Appveyor has a very clear documentation which allows you to easily set up your appveyor.yml file of copy a pre-configured file

Unlike Travis.yaml file, the appveyor.yml file requires a lot more commands to configure your project of C.I

Appveryor automates tests and gives notifications in case there errors in the project

It was the only pubic Windows CI service. Now, it is the best Windows CI service. It is free for all open source projects. It provides all functionalities out of box - enrollment mature, artifacts, persisted logs and more.

Long time ago, its running speed is to slow. However, after one service upgrade, the running speed increased. However, it is still a gap on running CI between AppVeyor Windows and Travis Linux. It need continue improving the running speed.

What problems are you solving with the product? What benefits have you realized?

- NuGet.Support

- Good integration with GitHub pull requests

- Configuration in YAML

- Deployment to custom environments

- best 4 Windows

- Safe with isolated build environments

- good customer support

- outstanding free service for open-source projects

- a bit slow than others

- need to support more operating systems

- No Java support

- No IDE integration

AppVeyor is Simple, Powerful and Great 4 Windows and GitHub.

I work mainly on open-source projects.

AppVeyor conducts all the tests on my code and keeps monitoring its status on every change.

On receiving a pull request, AppVeyor automatically checks for errors and reports if merging a pull request would break my code.

We've been using AppVeyor for over a year. We recently jumped up to 5 concurrent jobs, which really helps speed up our matrix builds. Pricing is simple. Support is superb. I really like that they have an integrated NuGet feed. We use it for build dependences and Chocolatey software installs. Setting up environments to deploy web app builds to Azure App Service is simple. Many developers at our company use AppVeyor for their open source projects too, so they are familiar with it, and some build scripts can be shared.

The updates have caused our builds to break a couple of times, but switching back to the previous image was just a single line change in appveyor.yml. At times, it would be useful to control the build image, or at least a layer on top of their's.

Definitely try it out. Take a look at many of the open source projects are currently using it. Just search for appveyor.yml in GitHub.

We use it for building all our software, automated testing (unit and some integration), continuous deployment, and all other deployments.

AppVeyor, with a simple Yaml config, will really help your team build and deploy on various environments. Complete console output helps you find problem when someone... breaks the build!

Lately, AppVayor had suffered from its growing popularity, and weird problems have occurred, making builds fail for no apparent reason. Their team has fixed most of them I would say, and things seem to be back to normal.

Consider premium package if you have a large team building many projects everyday.

Replacing local instances of Jenkins with AppVayor has let us put much less time in build machine installation, configuration, and management, and more time in REAL software development.

I love that I do not have to maintain the build servers. Once our build configuration was set up, I could just forget about it, and it just works. Aside from that, support is great--fast, and helpful. It is also great to have that peace of mind about the status of the build when performing pull requests into our "develop" branch. Additionally, I no longer have to build store-ready packages on my own machine. Now, no matter the status of my own enlistment, I can pull ready-to-publish appxupload packages out of the build artifacts in our release branches and publish them straight to the store. It saves me hours of work during release cycles, which happen now every four weeks.

My only wish would be tighter integration with HockeyApp. We currently deploy using a PowerShell script that I have written. In my experience, using custom scripts inside of CI is sometimes brittle. It hasn't failed so far in the two to three months since I set the whole system up, but if that integration were there, it would be one less thing to worry about.

Really dig into the trial to see if it meets your needs, and talk to support when you have pain points. Support is really helpful, and often they will implement things that are missing and preventing you from moving forward.

We are solving the problem of streamlining a continuous deployment of our mobile app. We need to push updates out every four weeks. In that world, catching build problems early and often, and being able to offload the actual building of the packages from our developers is extremely important. Two nice benefits materialized from this: QA always has the latest builds from "develop" without developer intervention, and our unit tests always get run, even when developers forget to do so.

Simple to get up and running and then very customisable, whatever you want to do with your builds. Oh and the support goes above and beyond everytime you need it.

UI could do with a bit of a facelift, but that's me being picky.

Do it, you won't regret it. Amazing bit of software, can't recommend highly enough.

Continuous integration and deployment. We were able to build a variety of projects from front-end JS, ASP.NET MVC and WPF apps to back-end services built with Web API, Service Stack, etc.

The ease of configuration. The fact that it's a hosted service is a massive plus because it means you don't have to manage the underlying infrastructure.

It needs more configuration options for parallel builds. I'd like to be able to limit the amount of builds per branch.

There's nothing better in terms of build automation out there in the marketplace. The VMs have everything you need in order build in most environments.

We use AppVeyor to build our products. We've quickly seen that AppVeyor's build time is considerably less than our previously TeamCity installation.

Unlike other CI services, AppVeyor has Windows-based infrastructure, which allows me to test my software on all major platforms. Setting up projects with appveyor.yml is straightforward and matches with how other similar non-Windows based services do configuration.

Appveyor's Python support is impressive as it offers several different Python versions including both 32 and 64 bit versions of Python, and Miniconda-based Python installations. The documentation associated with the Python environment is also well done and contains the information you need to get your builds running quickly.

Builds can be slow in the free version that does not allow concurrent jobs. The paid option allowing concurrent jobs is too expensive. While AppVeyor allows your to change what your configuration file is named, it does annoy me that the default is appveyor.yml, rather than a file prepended with a dot to make it hidden.

I would find it difficult to justify the expense of the Premium plan, but for open source projects, AppVeyor is great. If the lack of concurrent jobs is an issue, I would recommend limiting the number of tests that you run with AppVeyor. Do your detailed testing and generate coverage reports with another faster CI and use AppVeyor to ensure that your basic tests run in 32 and 64 bit Windows.

Windows is likely the most commonly used platform for our users, yet all of our developers use Mac OS X or Linux. AppVeyor ensures that our products still work in Windows without having to have a dedicated Windows build machine.

ability to build my linux applications under windows using cygwin or msys

not clear if / how to set up concurrent builds

it seems to be the only CI that can easily be configured to build windows applications

open source project - trying to be multi-platform compatible - appveyor has made this possible for me.