lupyuen/lupyuen.org
1
0
Fork 0
mirror of https://github.com/lupyuen/lupyuen.github.io.git synced 2025-01-13 03:18:31 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Update article

Browse source
This commit is contained in:
Lup Yuen Lee 2024-09-10 18:18:58 +08:00
parent 95c616bfe3
commit bcf1450e94
2 changed files with 9 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
images/nuttx-ci2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 70 KiB

14
src/ci.md
View file

@ -10,17 +10,17 @@ Suppose we [__Submit a Pull Request__](https://lupyuen.github.io/articles/pr) fo
That's why our Pull Request will trigger the __Continuous Integration Workflow__, to recompile NuttX for __All Hardware Platforms__.
([__1,594 Build Targets__](https://docs.google.com/spreadsheets/d/1OdBxe30Sw3yhH0PyZtgmefelOL56fA6p26vMgHV0MRY/edit?gid=0#gid=0) across Arm, RISC-V, Xtensa, AVR, i486, Simulator and more!)
That's [__1,594 Build Targets__](https://docs.google.com/spreadsheets/d/1OdBxe30Sw3yhH0PyZtgmefelOL56fA6p26vMgHV0MRY/edit?gid=0#gid=0) across Arm, RISC-V, Xtensa, AVR, i486, Simulator and more!
_What happens inside the Continuous Integration?_
Head over to the [__NuttX Repository__](https://github.com/apache/nuttx)...
1. Click [__GitHub Actions > Workflows > Build__](https://github.com/apache/nuttx/actions/workflows/build.yml)
- Click [__GitHub Actions > Workflows > Build__](https://github.com/apache/nuttx/actions/workflows/build.yml)
1. Click [__any one of the jobs__](https://github.com/apache/nuttx/actions/runs/10552464655)
- Click [__any one of the jobs__](https://github.com/apache/nuttx/actions/runs/10552464655)
1. Click [__Linux (arm-01) > Run Builds__](https://github.com/apache/nuttx/actions/runs/10552464655/job/29231352816)
- Click [__Linux (arm-01) > Run Builds__](https://github.com/apache/nuttx/actions/runs/10552464655/job/29231352816)
We'll see this __NuttX Build for Arm32__...
@ -114,7 +114,7 @@ Every single Pull Request will execute 24 Build Jobs in parallel.
Which needs __24 GitHub Runners__ per Pull Request. And [__they ain't cheap__](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates-for-standard-runners)!
TODO: Pic of NuttX Stats
![GitHub Runners for Apache NuttX RTOS](https://lupyuen.github.io/images/nuttx-ci2.png)
# Self-Hosted Runners
@ -223,6 +223,8 @@ Sadly the [__Linux Builds__](https://github.com/lupyuen3/runner-nuttx/actions/wo
We'll talk about Emulating x64 on macOS Arm64. But first we run Fetch Source on macOS...
![Continuous Integration for Apache NuttX RTOS](https://lupyuen.github.io/images/nuttx-ci.jpg)
# Fetch Source on macOS Arm64
_We haven't invoked the Runners for macOS Arm64?_
@ -349,6 +351,8 @@ Unless we create a Linux Arm64 Docker Image? Like for [__Compiling RISC-V Platfo
We'll chat about this in [__NuttX Discord Channel__](https://discord.com/channels/716091708336504884/1280436444141453313).
![Continuous Integration for Apache NuttX RTOS](https://lupyuen.github.io/images/nuttx-ci.jpg)
# What's Next
According to [__ASF Policy__](https://infra.apache.org/github-actions-policy.html): We should reduce to __15 Concurrent GitHub Runners__. How?