google/comprehensive-rust

Rewrite CI to only test languages that have actually changed

Open

#1,168 opened on Sep 5, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (32,954 stars) (2,009 forks)batch import
enhancementhelp wanted

Description

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?

Contributor guide

Tech stack
rustgithub actions
Domain
ci cdbuild systeminfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
GitHub Actionsbuild systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.