lupyuen commented on PR #18576: URL: https://github.com/apache/nuttx/pull/18576#issuecomment-4257325622
Thanks @hartmannathan! Sorry for messing up this complex discussion, maybe we should move it to the [Project TODOs](https://github.com/orgs/apache/projects/455/views/2). I think to roll out any meaningful updates to NuttX CI (like Build Dependency Caching) we need to... 1. Identify the __NuttX CI Lead__ who will implement, monitor and maintain these CI Enhancements 2. Sorry I can't be CI Lead: I suffer from hypertension and I can't commit to long-term projects. I believe @simbit18 might be busy with commitments (we should ask). So we might need to hunt for a suitable CI Lead. 3. To assist the CI Lead: We should nominate __Arch Owners__ (i.e. Owner for everything Arm32 / Arm64 / RISC-V / Xtensa / ...) and __Board Representatives__ (i.e. Representative for STM32 Boards / RP2040 Boards / IMX Boards / ...) 4. So it's easier for NuttX CI Lead to consult the Arch Owner on any CI Design Decisions. And Arch Owner can talk to the Board Reps, on behalf of CI Lead, [as explained here](https://youtu.be/JEF9_BqHWaY?si=lBM6RsMkw3agt7y5&t=3095). Can't find the ESP32 Downloads? We ask the Xtensa Owner :-) 5. As for __Non-ESP32 Downloads:__ NuttX has [73 curl commands](https://github.com/search?q=repo%3Aapache%2Fnuttx-apps+curl+language%3AMakefile&type=code&p=2&l=Makefile) for downloading Build Dependencies. We could rename the 73 `curl` commands to `nuttx-curl.sh`, which will read from our Dependency Cache. And ask Arch Owners + Board Reps to help test all 73 `nuttx-curl.sh` commands. 6. Remember: `nuttx-curl.sh` needs to support all kinds of Local PCs for development: macOS, WSL, Ubuntu, FreeBSD, etc. Maybe on Local PCs: We simply point `nuttx-curl.sh` to `curl`? 7. Will we have an __Operations Person__ (paid, preferably) to monitor NuttX CI daily? Like [checking the Daily Builds](https://github.com/apache/nuttx/issues/18659)? Making sure that Build Dependencies are cached correctly and updated often (e.g. due to security patches)? This person will affect our Upcoming CI Redesign. That's why I implemented CI Build Retry in the simplest way, that requires Zero Maintenance, Zero Monitoring. <img width="1910" height="1071" alt="vlcsnap-2026-03-09-09h04m27s740" src="https://github.com/user-attachments/assets/1a3565eb-997b-4ae8-a45b-5c6ff1c5d479"; /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
