Here's how Apache #NuttX RTOS is running Continuous Integration with GitHub Actions ... And why some Pull Requests might trigger 1,594 NuttX Builds!
Article: https://lupyuen.org/articles/ci.html
Apache #NuttX RTOS has 1,594 Targets across Arm, RISC-V, Xtensa, x64, ... Making sure they compile correctly? Gets super tricky
Article: https://lupyuen.org/articles/ci.html#one-thousand-build-targets
Self-Hosted GitHub Runners will work for Apache #NuttX Builds ... But kinda slow
Article: https://lupyuen.org/articles/ci.html#running-the-runners
Self-Hosted GitHub Runners will work on macOS Arm64 ... But #NuttX Continuous Integration requires Docker x64
Article: https://lupyuen.org/articles/ci.html#fetch-source-on-macos-arm64
Let's Emulate Ubuntu x64 on macOS Arm64 ... With UTM Emulator, very slooooowly
Article: https://lupyuen.org/articles/ci.html#utm-emulator-for-macos-arm64
Here's how Apache #NuttX RTOS is running Continuous Integration with GitHub Actions ... And why some Pull Requests might trigger 1,594 NuttX Builds!
@lupyuen I wonder how it would perform with an Alpine Linux guest 🤔
Let's experiment with GitHub Self-Hosted Runners ... To understand what happens inside Apache #NuttX Continuous Integration
Article: https://lupyuen.org/articles/ci.html#self-hosted-runners