zozo123 opened a new issue, #74163: URL: https://github.com/apache/airflow/issues/74163
Airflow already has several CI caching mechanisms, but source-only PR revisions can still rebuild expensive state even when the effective environment is unchanged. The direction here is to identify reusable CI state by the inputs that can actually change it, then reuse only trusted immutable state. Unknown or incomplete identity remains a cache miss and follows today’s build path. Related work / precedent: - #21103 — Breeze rebuild freshness based on important-file hashes. - #20741 — reuse Breeze CI-image building in CI. - #42999 — main-tip CI-image caching regression / fast rebuild behavior. - #74162 — Phase 0: logs a provisional environment fingerprint only. It does **not** enable reuse, skip builds, or skip tests. ### Milestones - **Complete the environment key:** base-image digests, effective build parameters, environment-affecting files, and dependency freshness. - **Measure before rollout:** key matches, miss reasons, build/materialization costs, and actual workflow critical-path savings. - **Prove current-revision correctness:** shadow comparisons using identical tests, including imports and package metadata. - **Enable trusted reuse:** main publishes immutable artifacts; forks read only. Missing/unavailable artifacts, ambiguous identity, or incompatible jobs fall back to today’s build. - **Define constraints reuse separately:** give constraints their own identity and validate reuse independently. ### Acceptance criteria - Preserve current test coverage. - No test pruning and no Bazel dependency. - Validate in shadow mode before rollout. - Provide immediate rollback/fallback to the current build path. - Kubernetes coverage remains required. - Do not assume or promise a particular cache-hit rate or minute-scale CI; measure first. This issue does **not** block #74162. That PR should stay a small observational primitive while the complete reuse contract is designed and validated. -- 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]
