Context
Currently, stellar-cli accounts for half of all CI usage in stellar company repositories. Notably, half of this CI consumption is attributed to "MacOS runners." This suggests that we may be performing redundant work multiple times (e.g., repeated builds without effective caching) or running tests with minimal ROI, especially in the context of PRs.
Proposal
- Analyze CI workflows to identify and reduce redundant builds and tests, focusing on MacOS runners.
- Implement caching strategies to prevent unnecessary rebuilds.
- Audit test cases, particularly those triggered by PRs, and evaluate their necessity and ROI.
- Recommend changes to CI configuration that reduce cost and time spent on low-value jobs.
Goal
Reduce overall CI usage and costs by streamlining build and test processes, prioritizing MacOS runner efficiency, and eliminating low-value or repeated tasks.
This issue is a sub-issue of #2164 and should help address the high CI build and test times and inefficiencies reported there.
Context
Currently, stellar-cli accounts for half of all CI usage in stellar company repositories. Notably, half of this CI consumption is attributed to "MacOS runners." This suggests that we may be performing redundant work multiple times (e.g., repeated builds without effective caching) or running tests with minimal ROI, especially in the context of PRs.
Proposal
Goal
Reduce overall CI usage and costs by streamlining build and test processes, prioritizing MacOS runner efficiency, and eliminating low-value or repeated tasks.
This issue is a sub-issue of #2164 and should help address the high CI build and test times and inefficiencies reported there.