Andrushika opened a new pull request, #71886:
URL: https://github.com/apache/airflow/pull/71886

   ## Why
   I was using git worktree for my dev. Currently, when I execute `breeze 
airflow-start` in a different worktree, breeze force rebuild the image every 
time, even if the same image already exists. It wastes a lot of time.
   Breeze records whether the CI image was built in the per-checkout `.build/` 
directory. The image itself is shared by every checkout through the same Docker 
daemon. So a fresh git worktree always force-rebuilds an image that another 
checkout already built from identical sources.
   
   ## What
   
   `breeze ci-image build` now adds a label with the aggregated hash of the 
files that trigger rebuilds. The hash covers relative paths and file contents 
only, so it is stable across checkouts. When the local build marker or md5 
cache is missing or stale, breeze compares that label with the current sources 
and reuses the image on match. Images built before this change have no label 
and keep the current behavior. The label can only skip a build, never force one.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Fable 5)
   
   Generated-by: Claude Code (Fable 5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
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]

Reply via email to