The-Homebrew-Cloud/skyline
2
0
Fork 0
mirror of https://github.com/skyline-emu/skyline.git synced 2024-11-05 11:25:07 +01:00
Code Issues Packages Projects Releases Wiki Activity
d1a682eace
skyline/.github/workflows/ci.yml

100 lines
3.8 KiB
YAML
Raw Normal View History

Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
name: CI
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
on: [ push, pull_request ]
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
jobs:
build:
runs-on: ubuntu-latest
env:
JVM_OPTS: -Xmx6G
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
IS_SKYLINE_SIGNED: ${{ secrets.KEYSTORE != '' }}
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
steps:
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
- name: Git Checkout
uses: actions/checkout@v2
with:
submodules: recursive
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
- name: Restore Gradle Cache
Update CI to use cache@v3 + ignore partial matches of cache key
2022-04-07 11:21:01 +02:00
uses: actions/cache@v3
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
with:
Extend CI Gradle caching and performance parameters A lot of default Gradle parameters are unoptimal for the best performance, this enables the configuration and build cache alongside parallel building.
2022-05-30 19:18:34 +02:00
path: ~/.gradle/
Add Robust CI Cache Restoration The `restore-keys` parameter of `actions/cache@v3` is now utilized to add robust fallbacks for missing cache keys, it should automatically fall back to an older but still valid cache rather than entirely miss now.
2022-05-30 20:58:40 +02:00
key: ${{ runner.os }}-gradle-${{ hashFiles('**/build.gradle') }}-${{ hashFiles('app/**/*.xml') }}-${{ hashFiles('app/**.kt', 'app/**.java') }}
restore-keys: |
${{ runner.os }}-gradle-${{ hashFiles('**/build.gradle') }}-${{ hashFiles('app/**/*.xml') }}-
${{ runner.os }}-gradle-${{ hashFiles('**/build.gradle') }}-
${{ runner.os }}-gradle-
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
- name: Restore CXX Cache
Update CI to use cache@v3 + ignore partial matches of cache key
2022-04-07 11:21:01 +02:00
uses: actions/cache@v3
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
with:
Extend CI C++ build cache The CI didn't cache the C++ build related directories under `app/build/` which caused a full recompilation of C++ code, this takes a significant amount of time.
2022-05-30 19:17:07 +02:00
path: |
app/.cxx/
app/build/intermediates/cxx/
Add Robust CI Cache Restoration The `restore-keys` parameter of `actions/cache@v3` is now utilized to add robust fallbacks for missing cache keys, it should automatically fall back to an older but still valid cache rather than entirely miss now.
2022-05-30 20:58:40 +02:00
key: ${{ runner.os }}-cxx-${{ hashFiles('app/**/CMakeLists.txt') }}-${{ hashFiles('app/**/*.h', 'app/**/*.hpp', 'app/**/*.cpp', 'app/**/*.S') }}
restore-keys: |
${{ runner.os }}-cxx-${{ hashFiles('app/**/CMakeLists.txt') }}-
${{ runner.os }}-cxx-
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
Upgrade AGP to `7.1.0-beta01` & NDK to `24.0.7856742` We've moved to using a beta AGP as `7.0.2` is breaks `clangd` and other C++ features on Beta/Canary Android Studio. NDK was additionally updated with `mbedtls` to fix warnings caused by it alongside some other minor fixes to code for newer versions of libcxx. The new AGP has a bug where it does not look for executables specified in `android_gradle_build.json` in `PATH` that includes `ninja` which is provided by the `ninja-build` package on the system rather than Android SDK's CMake on GitHub Actions (Ubuntu 20.04). This has been fixed by symlinking `/usr/bin/ninja` to the project root which is searched in for the `ninja` executable.
2021-10-31 00:03:27 +02:00
- name: Install Ninja Build
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
run: |
sudo apt-get install -y ninja-build
Upgrade AGP to `7.1.0-beta01` & NDK to `24.0.7856742` We've moved to using a beta AGP as `7.0.2` is breaks `clangd` and other C++ features on Beta/Canary Android Studio. NDK was additionally updated with `mbedtls` to fix warnings caused by it alongside some other minor fixes to code for newer versions of libcxx. The new AGP has a bug where it does not look for executables specified in `android_gradle_build.json` in `PATH` that includes `ninja` which is provided by the `ninja-build` package on the system rather than Android SDK's CMake on GitHub Actions (Ubuntu 20.04). This has been fixed by symlinking `/usr/bin/ninja` to the project root which is searched in for the `ninja` executable.
2021-10-31 00:03:27 +02:00
ln -s /usr/bin/ninja .
- name: Install CMake & Android NDK
Update NDK (25.0.8221429) + Gradle (7.4.1) + Build Tools (33.0.0)
2022-03-29 10:26:36 +02:00
run: echo "yes" | $ANDROID_HOME/tools/bin/sdkmanager "cmake;3.18.1" "ndk;25.0.8221429" --channel=3 | grep -v = || true
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
Introduce CI build signing We've done no signing of any Skyline APKs to date which causes issues regarding authenticity of any APKs as they could be entirely unofficial builds which have not been vetted by the team. Additionally, the different keys remove the ability to reinstall a different build successively as Android checks for matching signatures before installing an APK.
2022-05-30 17:23:17 +02:00
- name: Decode Keystore
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
if: ${{ env.IS_SKYLINE_SIGNED == 'true' }}
Introduce CI build signing We've done no signing of any Skyline APKs to date which causes issues regarding authenticity of any APKs as they could be entirely unofficial builds which have not been vetted by the team. Additionally, the different keys remove the ability to reinstall a different build successively as Android checks for matching signatures before installing an APK.
2022-05-30 17:23:17 +02:00
env:
KEYSTORE_ENCODED: ${{ secrets.KEYSTORE }}
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
run: echo $KEYSTORE_ENCODED | base64 --decode > "/home/runner/keystore.jks"
Introduce CI build signing We've done no signing of any Skyline APKs to date which causes issues regarding authenticity of any APKs as they could be entirely unofficial builds which have not been vetted by the team. Additionally, the different keys remove the ability to reinstall a different build successively as Android checks for matching signatures before installing an APK.
2022-05-30 17:23:17 +02:00
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
- name: Android Assemble
Introduce CI build signing We've done no signing of any Skyline APKs to date which causes issues regarding authenticity of any APKs as they could be entirely unofficial builds which have not been vetted by the team. Additionally, the different keys remove the ability to reinstall a different build successively as Android checks for matching signatures before installing an APK.
2022-05-30 17:23:17 +02:00
env:
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
SIGNING_STORE_PATH: "/home/runner/keystore.jks"
Introduce CI build signing We've done no signing of any Skyline APKs to date which causes issues regarding authenticity of any APKs as they could be entirely unofficial builds which have not been vetted by the team. Additionally, the different keys remove the ability to reinstall a different build successively as Android checks for matching signatures before installing an APK.
2022-05-30 17:23:17 +02:00
SIGNING_STORE_PASSWORD: ${{ secrets.SIGNING_STORE_PASSWORD }}
SIGNING_KEY_ALIAS: ${{ secrets.SIGNING_KEY_ALIAS }}
SIGNING_KEY_PASSWORD: ${{ secrets.SIGNING_KEY_PASSWORD }}
Extend CI Gradle caching and performance parameters A lot of default Gradle parameters are unoptimal for the best performance, this enables the configuration and build cache alongside parallel building.
2022-05-30 19:18:34 +02:00
run: ./gradlew --stacktrace --configuration-cache --build-cache --parallel --configure-on-demand assemble
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
- name: Rename APKs (Signed)
if: ${{ env.IS_SKYLINE_SIGNED == 'true' }}
Make CI APK name more verbose Adds the CI run number to the APK name, they were `app-(debug/release).apk` but are now `skyline-${CI run number}-(debug/release).apk`. This makes it significantly easier to identify what version a specific build is, this alongside signing consolidates Skyline builds.
2022-05-30 17:40:22 +02:00
run: |
mv app/build/outputs/apk/debug/app-debug.apk skyline-$GITHUB_RUN_NUMBER-debug.apk
mv app/build/outputs/apk/release/app-release.apk skyline-$GITHUB_RUN_NUMBER-release.apk
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
- name: Upload Signed Debug APK
if: ${{ env.IS_SKYLINE_SIGNED == 'true' }}
Make CI APK name more verbose Adds the CI run number to the APK name, they were `app-(debug/release).apk` but are now `skyline-${CI run number}-(debug/release).apk`. This makes it significantly easier to identify what version a specific build is, this alongside signing consolidates Skyline builds.
2022-05-30 17:40:22 +02:00
uses: actions/upload-artifact@v3
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
with:
Make CI APK name more verbose Adds the CI run number to the APK name, they were `app-(debug/release).apk` but are now `skyline-${CI run number}-(debug/release).apk`. This makes it significantly easier to identify what version a specific build is, this alongside signing consolidates Skyline builds.
2022-05-30 17:40:22 +02:00
name: skyline-${{ github.run_number }}-debug.apk
path: skyline-${{ github.run_number }}-debug.apk
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
- name: Upload Signed Release APK
if: ${{ env.IS_SKYLINE_SIGNED == 'true' }}
Make CI APK name more verbose Adds the CI run number to the APK name, they were `app-(debug/release).apk` but are now `skyline-${CI run number}-(debug/release).apk`. This makes it significantly easier to identify what version a specific build is, this alongside signing consolidates Skyline builds.
2022-05-30 17:40:22 +02:00
uses: actions/upload-artifact@v3
Replace skyline-emu/VkHpp with KhronosGroup/Vulkan-Hpp We used a custom version of Vulkan-Hpp which split the files a lot prior to avoid any developers needing to manually set IDE settings for IntelliJ to work but this wasn't practical due to how it required modifications to Vulkan-Hpp's generator which would make maintenance extremely difficult. It was determined that we should just add the requirement for changing the IDE settings and use Vulkan-Hpp directly.
2021-03-26 19:12:19 +01:00
with:
Make CI APK name more verbose Adds the CI run number to the APK name, they were `app-(debug/release).apk` but are now `skyline-${CI run number}-(debug/release).apk`. This makes it significantly easier to identify what version a specific build is, this alongside signing consolidates Skyline builds.
2022-05-30 17:40:22 +02:00
name: skyline-${{ github.run_number }}-release.apk
path: skyline-${{ github.run_number }}-release.apk
Move to GitHub Actions for CI This commit adds a GitHub Actions Workflow for Continuous Integration.
2019-12-11 18:02:42 +01:00
Handle unsigned builds on CI We don't always have access to CI secrets, such as, when a certain CI action is triggered by a PR from an external repository then it won't have access to secrets and be signed. While we likely will allow for this in the future as all workflows do have to be approved, it is still important to not crash when keys are unavailable and have a graceful fallback for those situations.
2022-06-11 13:35:20 +02:00
- name: Rename APKs (Unsigned)
if: ${{ env.IS_SKYLINE_SIGNED == 'false' }}
run: |
mv app/build/outputs/apk/debug/app-debug.apk skyline-$GITHUB_RUN_NUMBER-unsigned-debug.apk
mv app/build/outputs/apk/release/app-release.apk skyline-$GITHUB_RUN_NUMBER-unsigned-release.apk
- name: Upload Unsigned Debug APK
if: ${{ env.IS_SKYLINE_SIGNED == 'false' }}
uses: actions/upload-artifact@v3
with:
name: skyline-${{ github.run_number }}-unsigned-debug.apk
path: skyline-${{ github.run_number }}-unsigned-debug.apk
- name: Upload Unsigned Release APK
if: ${{ env.IS_SKYLINE_SIGNED == 'false' }}
uses: actions/upload-artifact@v3
with:
name: skyline-${{ github.run_number }}-unsigned-release.apk
path: skyline-${{ github.run_number }}-unsigned-release.apk
Reference in New Issue Copy Permalink