The distributed test farm has just started and I am amazed Lup already made working prototype in just few days :-)
If you have spare resources for external CI builder that could be attached to GH repo and have time to set them up please let us know! :-) There are many things to consider for distributed farm: * we need some architecture. * we may need to interconnect with GitHub, but also work independent of GitHub. * this distributed farm may have dynamic nodes that will not always be available so we cannot depend and block PR for instance. * distributed farm will not only allow build test, but more importantly runtime tests on a real hardware.. so we also need some architecture, scripting, tools for automation and results analysis, etc. * This solution should be multiplatform so it works on preferred end user OS (i.e. Linux, BSD, macOS, Windows). * For end-user this should be out-of-the-box solution, ready for use images needs to be created, either as OS image to use or some installer that will set all thing, including cross platform build toolchains, etc. * etc etc.. it will be a long but interesting road :-) I really like Lup's small steps with working results approach with that is possible and at hand at the moment then it can grow in small measurable steps with time :-) Have a good weekend :-) Tomek On Sun, Nov 10, 2024 at 12:18 AM Ludovic Vanasse <ludovicvana...@gmail.com> wrote: > > Yes, thank you very much, Lup! > > Maybe a question for you, I like the idea of NuttX dev hosting the build > for the PR, it helps avoid the limitation of the number of runner that ASF > allocate us (which I'm grateful for). But from my understanding, we are > running the CI for different targets and uploading it to the dashboard. I > was wondering if we could maybe also host our own GitHub CI runner ( > https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners)? > Maybe that would cut the middle-man the dashboard serve at the moment. Just > a thought, and I'm curious what you think. > > Thanks again for all your excellent work! > > Ludovic Vanasse > ludovicvana...@gmail.com > +1(514) 475-0447 > > > On Sat, Nov 9, 2024 at 6:12 PM Tomek CEDRO <to...@cedro.info> wrote: > > > BIG THANK YOU LUP FOR SAVING THE NUTTX GH CI !! :-) > > > > On the good side we started working on distributed build and test > > farm.. Your https://nuttx-dashboard.org/ is already working so we are > > prepared now for worst case scenario.. I am sure this project will > > grow and bring not only build but also functional testing soon and > > this will result in even better NuttX implementations :-) > > > > Once again big thank you!! :-) > > Tomek > > > > > > > > On Sat, Nov 9, 2024 at 11:16 PM Lee, Lup Yuen <lu...@appkaki.com> wrote: > > > > > > Within Two Weeks: We squashed our GitHub Actions spending from $4,900 > > (weekly) down to $890. Thank you everyone for helping out, we saved our > > Continuous Integration Servers from shutdown! 🎉 > > > > > > This article explains everything we did in the (Semi-Chaotic) Two Weeks: > > > > > > (1) Shut down the macOS and Windows Builds, revive them in a different > > form > > > > > > (2) Merge Jobs are super costly, we moved them to the NuttX Mirror Repo > > > > > > (3) We Halved the CI Checks for Complex PRs. (Continuous Integration) > > > > > > (4) Simple PRs are already quite fast. (Sometimes 12 Mins!) > > > > > > (5) Coding the Build Rules for our CI Workflow, monitoring our CI > > Servers 24 x 7 > > > > > > (6) We can’t run All CI Checks, but NuttX Devs can help ourselves! > > > > > > Please check out the article: > > https://lupyuen.codeberg.page/articles/ci3.html > > > > > > > > > > > > Lup > > > > > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
