google/comprehensive-rust

Rewrite CI to only test languages that have actually changed

Open

#1,168 opened on 2023年9月5日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)Rust (32,954 stars) (2,009 forks)batch import
enhancementhelp wanted

説明

We currently build and test all translations — resulting in some 32 GitHub workflows being executed per PR. This is often unnecessary when only the original English text changes.

I'm considering if it would be worth it to use a big build system such as Bazel. This would allow us to get very fine-grained dependency tracking and this would allow us to skip unnecessary steps. However, I believe it will be significantly more complex to maintain the build system files that way.

Thoughts or ideas?

コントリビューターガイド

技術スタック
rustgithub actions
領域
ci cdbuild systeminfrastructure
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
GitHub Actionsbuild systems
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
35
調査方針
Investigate the current CI workflows in .github/workflows/ to see which languages are tested and how they are triggered. Consider using GitHub Actions path filters to run jobs only when relevant files change. Evaluate the feasibility of a simpler solution before moving to Bazel. Discuss ideas in the issue comments.