# AppVeyor CI

**URL:** <https://discourse.numenta.org/t/appveyor-ci/2095>\
**Category:** NuPIC\
**Tags:** windows, ci\
**Created:** [April 5, 2017, 5:44pm UTC](https://discourse.numenta.org/t/appveyor-ci/2095 "2017-04-05T17:44:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhyolight](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.numenta.org/rhyolight/32/3922_2.png) [@rhyolight](https://discourse.numenta.org/u/rhyolight)\
**Post date:** [April 5, 2017, 5:44pm UTC](https://discourse.numenta.org/t/appveyor-ci/2095/1 "2017-04-05T17:44:58Z")

</div>

We use [AppVeyor-CI](http://www.appveyor.com/) for our Windows related builds and validation of PRs (pull-requests). With [Travis-CI](https://travis-ci.org/) used for Linux related building and testing. The AppVeyor environment for builds is documented [here](http://www.appveyor.com/docs/build-configuration).

## AppVeyor is Running for:

- [`nupic.core`](https://ci.appveyor.com/project/numenta-ci/nupic-core/history)
- [`nupic`](https://ci.appveyor.com/project/numenta-ci/nupic/history)

Travis-CI equivalent links:

- [`nupic.core`](https://travis-ci.org/numenta/nupic.core/)
- [`nupic`](https://travis-ci.org/numenta/nupic/)

## Run AppVeyor CI on your forks

It’s easy to run the nupic build process using AppVeyor-CI (AV) on your forks. You’ll need to [create an appveyor account](http://www.appveyor.com/) first, then fork nupic and/or nupic.core. In your local fork, you’ll have the `appveyor.yaml` file, which is configured to run on every branch except master (you don’t have to touch it). To enable appveyor on your fork, [go to your projects](https://ci.appveyor.com/projects/) and click the switch for ‘New Project’ and add your NuPIC or NuPIC.Core fork. You should see an appveyor build running any time you push to branches on your fork.

Also, when you submit a [PR against master](https://github.com/numenta/nupic/pulls), appveyor will run against the PR whether you’ve set up an appveyor account or not. During this time, there is an indication on github that the pull request may not be safe to merge. Once the travis and appveyor builds pass, the warning is replaced by a “good to merge” note.