AppVeyor

AppVeyor is a CI/CD service for Windows and .NET developers, used hosted or self-hosted as AppVeyor Server, with plans sized by concurrent build jobs.

AppVeyor runs a build, its tests and its deployment each time code is pushed, following steps written in an appveyor.yml file that lives in the repository. The service belongs to AppVeyor Systems Inc., a privately held and self-funded Canadian corporation in Vancouver, founded in 2011. Its continuous integration tools are made for Windows developers. The same service builds public open-source projects and private company code. A new commit or tag starts a build on its own, and pull request builds have settings of their own for which events count. A build matrix fans one configuration out into several jobs, which run in parallel when the account allows more than one concurrent job. Build cache keeps chosen folders and files between builds, so dependencies are not downloaded again, and scheduled builds follow a cron expression set in UTC. Artifacts packaged by a build feed the deployment steps that follow and can be downloaded through the API afterwards. Bring Your Own Cloud (BYOC) adds an existing workstation, cloud VM or office server as a build machine beside the hosted ones. AppVeyor fits Windows and .NET teams that want their build defined in the repository rather than in a web form. Open-source maintainers use the hosted service for public projects, and companies use it for private repositories. AppVeyor Server is the route for organisations that need the build system inside their own network or cloud account. It is installed from a download rather than signed up for online, and it is a version of the hosted service that runs on the customer's own server. A common pipeline builds a .NET library on each pull request, runs its tests and publishes the package to NuGet when a release tag is pushed. Code arrives from GitHub, GitHub Enterprise, Bitbucket, GitLab, Azure Repos or Gitea, wherever a team already keeps it. Finished artifacts then travel to Azure or AWS through the deployment steps. That suits a Windows team that wants every release to come from a build it can trace back to a single commit.