Switch to Github Actions from AppVeyor #7

Merged
Xaymar merged 3 commits from ci-github into master 2019-10-31 05:53:35 +01:00
Xaymar commented 2019-10-31 05:36:49 +01:00 (Migrated from github.com)

Description

AppVeyor is slow to react, slow to build and slow to generally do anything. Even a Raspberry Pi can finish building faster than AppVeyor even reacts to a new build. Therefore, this switches out AppVeyor with Github Actions.

Motivation and Context

How Has This Been Tested?

Types of changes

Checklist:

  • My code has been run through clang-format.
  • I have read the contributing document.
  • My code is not on the master branch.
  • The code has been tested.
  • All commit messages are properly formatted and commits squashed where appropriate.
<!--- Please fill out the following template, which will help other contributors review your Pull Request. --> <!--- Make sure you’ve read the contribution guidelines --> ### Description AppVeyor is slow to react, slow to build and slow to generally do anything. Even a Raspberry Pi can finish building faster than AppVeyor even reacts to a new build. Therefore, this switches out AppVeyor with Github Actions. <!--- Describe your changes in detail. --> <!--- If this change includes UI elements, please include screenshots. --> ### Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open Mantis issue, or implements feature request --> <!--- from the Ideas page, please link to the issue here. --> ### How Has This Been Tested? <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment (hardware, OS version, etc.),--> <!--- and the tests you ran, including how it may affect other areas of code. --> ### Types of changes <!--- What types of changes does your PR introduce? Uncomment all that apply --> <!--- - Bug fix (non-breaking change which fixes an issue) --> <!--- - New feature (non-breaking change which adds functionality) --> <!--- - Performance enhancement (non-breaking change which improves efficiency) --> <!--- - Code cleanup (non-breaking change which makes code smaller or more readable) --> <!--- - Breaking change (fix or feature that would cause existing functionality to change) --> <!--- - Documentation (a change to documentation pages) --> ### Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My code has been run through [clang-format](https://github.com/obsproject/obs-studio/blob/master/.clang-format). - [x] I have read the [**contributing** document](https://github.com/obsproject/obs-studio/blob/master/CONTRIBUTING.rst). - [x] My code is not on the master branch. - [x] The code has been tested. - [ ] All commit messages are properly formatted and commits squashed where appropriate.
Sign in to join this conversation.