Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

AppVeyor: Continuous Integration in Your GitHub Projects

DZone's Guide to

AppVeyor: Continuous Integration in Your GitHub Projects

Learn how to get started with AppVeyor, a CI platform you can connect with your GitHub repos to facilitate continuous integration.

· DevOps Zone ·
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

Navigating through the GitHub repositories, I always notice this Build icon and try to imagine the origin of it! In this article, I will cover only part of Build of the project, because this type of tool has several features and they are worth looking at one by one.

AppVeyor is a Continuous Integration platform which makes it much easier for developers to test, deploy, and monitor their builds, tests, and more.

The first step is to access the site and log in, as my goal was to connect my GitHub with their service I used the same to register.

In Main Menu click on “New Project”:

As you can see, it is possible to connect several platforms to AppVeyor: GitHub, Bitbucket, VSTS, and others.

As my GitHub account was already connected, it shows the repositories I have. I’ll choose one of them to display step-by-step:

Click on Settings to access the configuration:

Within Settings, you can configure which branches you want to integrate; it is worth surfing a little to better understand what each one does.

Like most of our projects, we use Nuget packages; we have to do the restore before starting the build, so to configure it is very simple:

Return to the main screen and click New Build:

The build will take place and you can follow the steps through the console window.

The main screen will look like this after setting up some repositories:

Readme.MD

Now let’s put the Build information of your repository into your Readme file.

[![Build Status]( https://img.shields.io/appveyor/ci/USERNAME/REPOSITORIO/master.svg)](https://ci.appveyor.com/project/USERNAME/REPOSITORIO)

Replace the information with your account and you’re done! Every time you update your repository, a new build will start.

See you all!

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:
appveyor ,github ,devops ,tutorial ,continuous integration ,ci/cd

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}