trns1997 commented on PR #17197: URL: https://github.com/apache/nuttx/pull/17197#issuecomment-3437510618
> > Overall, the main gain is predictable CI execution and significant cost reduction by avoiding redundant runs, especially for the build stage, which is the most time- and cost-intensive. Maybe this can help us adhere to the ASF policy for Github Actions as mentioned here https://lupyuen.org/articles/ci3#appendix-build-rules-for-ci-workflow > > Sorry can you give me an example of a specific build (e.g. RP2040) and how it might avoid redundant runs with the new system? > > I'm most concerned about the [NuttX Release Process](https://github.com/apache/nuttx/issues/14062). NuttX CI must complete 100% of the Release Branch Builds, and we need to be informed ASAP if any build breaks (hence the massively parallel builds). Thanks! @lupyuen Thanks — great question! Here’s a run showing how the new workflow behaves: https://github.com/apache/nuttx/actions/runs/18410848280?pr=17184 You can see that draft PRs skip the rest of the pipeline, and if **check** or **lint** fail, the **build** stage doesn’t start. This avoids spinning up heavy builds when they’re not needed. For release branches, we still need the massive parallel builds to ensure full coverage — that’s unavoidable. The goal here is to reduce how often those parallel jobs run unnecessarily during normal PR development (for example, on drafts or failed checks), not to remove or serialize them completely. Once this structure proves stable, we can add branch-based conditions to better separate dev vs release behavior while keeping both efficient (not sure what it would look like but this is a bonus). That said, if you guys feel the added value here is minimal or it's too hard to integrate, I’m happy to leave the current workflow as is :). -- 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]
