ci: Integrate Github Actions as a CI provider #2

Merged
Xaymar merged 1 commits from ci into master 2019-09-04 00:30:07 +02:00
Xaymar commented 2019-09-04 00:28:09 +02:00 (Migrated from github.com)

Description

Integrates Github Actions as a CI provider for future use, while also splitting packaging and building apart for better workflow.

The build script additionally now properly follows the build chain for x32 and x64 independently and will not try to build architectures for which there is no generator set.

Motivation and Context

Relying on compilation results from AppVeyor is way too slow, with up to 10 minutes delay for a single commit to build. It only gets worse the more commits there are, which isn't great. Therefore AppVeyor is now only used for releasing tags until that can also be moved over to Github Actions.

How Has This Been Tested?

Extensively over several commits. Code is currently not compatible with Visual Studio 2019, which needs to be fixed.

Types of changes

  • New feature (non-breaking change which adds functionality)

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 <!--- Describe your changes in detail. --> <!--- If this change includes UI elements, please include screenshots. --> Integrates Github Actions as a CI provider for future use, while also splitting packaging and building apart for better workflow. The build script additionally now properly follows the build chain for x32 and x64 independently and will not try to build architectures for which there is no generator set. ### 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. --> Relying on compilation results from AppVeyor is way too slow, with up to 10 minutes delay for a single commit to build. It only gets worse the more commits there are, which isn't great. Therefore AppVeyor is now only used for releasing tags until that can also be moved over to Github Actions. ### 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. --> Extensively over several commits. Code is currently not compatible with Visual Studio 2019, which needs to be fixed. ### 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! --> - [x] 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. - [x] All commit messages are properly formatted and commits squashed where appropriate.
Sign in to join this conversation.