acassis commented on issue #17914: URL: https://github.com/apache/nuttx/issues/17914#issuecomment-3818110731
> Hmmm... > (1) How will we ensure that the SBCs are running continuously? What happens if they are shut down? How do we ensure that they are running the latest versions of the CI Scripts? If CI could submit the request it means the board is off. A better option should have a heart beat from the nodes, so we could know if a board turned off during the build process > (2) How will we prevent the SBCs from running any Malicious Code embedded in the PRs? We are not consuming any code from those SBC, the idea is just ask them to build, test and return the result. We will not received the generated firmware. > (3) This still requires revamping NuttX CI. Which we lack expertise and the 24 x 7 continuous monitoring. True, that is a valid point, we need master it. I think currently all knowledge is with you and @simbit18, in the past it was with Brennan. And we don't have a good Documentation about it. > (4) I have a hunch that Arm64 SBCs are quite slow at compiling NuttX Code. That's why I'm now running [NuttX Build Farm](https://lupyuen.org/articles/ci2) on a Refurbished Intel Xeon Ubuntu Server. Yes, I think Xeon are faster, probably because it has more processing power and/or gcc and other toolchain tools are optimized to it. But we need to consider which is more energetically efficient: total work done / total power consumption. -- 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]
