summaryrefslogtreecommitdiffstats
path: root/.ci/yuzu-mainline-step2.yml (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-08-30ci: Enable building with Visual Studio 2022 (again)Morph1-1/+1
Since the following https://developercommunity.visualstudio.com/t/Type-alias-lookup-failure-within-paramet/10039150 compiler bug has been fixed, we can finally build with VS 2022 again.
2022-07-27chore: make yuzu REUSE compliantAndrea Pappacoda1-0/+3
[REUSE] is a specification that aims at making file copyright information consistent, so that it can be both human and machine readable. It basically requires that all files have a header containing copyright and licensing information. When this isn't possible, like when dealing with binary assets, generated files or embedded third-party dependencies, it is permitted to insert copyright information in the `.reuse/dep5` file. Oh, and it also requires that all the licenses used in the project are present in the `LICENSES` folder, that's why the diff is so huge. This can be done automatically with `reuse download --all`. The `reuse` tool also contains a handy subcommand that analyzes the project and tells whether or not the project is (still) compliant, `reuse lint`. Following REUSE has a few advantages over the current approach: - Copyright information is easy to access for users / downstream - Files like `dist/license.md` do not need to exist anymore, as `.reuse/dep5` is used instead - `reuse lint` makes it easy to ensure that copyright information of files like binary assets / images is always accurate and up to date To add copyright information of files that didn't have it I looked up who committed what and when, for each file. As yuzu contributors do not have to sign a CLA or similar I couldn't assume that copyright ownership was of the "yuzu Emulator Project", so I used the name and/or email of the commit author instead. [REUSE]: https://reuse.software Follow-up to 01cf05bc75b1e47beb08937439f3ed9339e7b254
2022-07-23Revert "ci: Enable building with Visual Studio 2022"bunnei1-1/+1
2022-04-25ci: Update vmImage to windows-2022Morph1-1/+1
The windows-2022 image contains Visual Studio 2022.
2021-10-11ci: Use ubuntu-latest vmImage where applicableameerj1-0/+2
Not specifying the vmImage defaults to ubuntu-16.04, which will be deprecated soon and is experiencing brownouts.
2021-07-21ci: Increase mainline build timeout.bunnei1-1/+3
- We're currently timing out with builds exceeding 60M. This doubles the timeout to 120M.
2020-04-04ci: Update to Windows Server 2019 and Visual Studio 2019Zach Hilman1-1/+1
This updates to the latest available toolchain for MSVC builds.
2019-10-09ci: Isolate upload merge step into stage 2Zach Hilman1-2/+2
2019-10-05ci: Add version counter variableZach Hilman1-0/+5
2019-10-03ci: Correct mainline release dependencyZach Hilman1-1/+3
2019-10-03ci: Use MSVC windows for patreonZach Hilman1-1/+1
2019-10-02ci: Use MSVC windows for mainlineZach Hilman1-3/+36
2019-09-22ci: Split mainline pipeline and add support for GitHub releases (#2900)Zach Hilman1-6/+9
* ci: Add mock build alternative for fast testing * ci: Always cache build * ci: Extract steps to download build stage artifacts * ci: Add template to release to GitHub * ci: Add template to release to Azure Universal Artifacts * ci: Split mainline to two pipelines
2019-07-28ci: Fix Azure PR BuildsZach Hilman1-0/+2
2019-07-14Finalize Azure Pipelines DefinitionsZach Hilman1-16/+20
d
2019-07-10Add Pipeline DefinitionsZach Hilman1-0/+0
2019-07-10Set up CI with Azure PipelinesFlame Sage1-0/+19
[skip ci]
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 09:59:09 +0100