Skip to content

feat: Improve bazel caching#137

Draft
lurtz wants to merge 30 commits into
mainfrom
improved-caching-part-2
Draft

feat: Improve bazel caching#137
lurtz wants to merge 30 commits into
mainfrom
improved-caching-part-2

Conversation

@lurtz

@lurtz lurtz commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

At the moment the bazel caches can become huge and outdated at the same time. Thus this changes the cache handling as follows:

  • repository cache keying is unchanged. However the user repository needs a job, which rebuilds it when especially the MODULE.bazel.lock changes. Otherwise it will be incomplete and some jobs still need to download stuff from the internet instead of reusing the cache.
  • disk cache keying is changed to a timestamp based one and is unique per job. After each job run an updated cache is pushed.

This requires the presence of a dedicated cache maintenance job. This must at least rebuild the repository cache on MODULE.bazel.lock changes. In addition it shall delete the disk caches to ensure their growth is limited and outdated files are removed.

This supersedes #133, which should only be touched carefully until inc_someip_gateway switches to uses git revisions again.

TODO

  • use revisions from cicd-actions after corresponding PRs have been merged

@lurtz
lurtz force-pushed the improved-caching-part-2 branch from 57f1b4b to 005276f Compare July 16, 2026 14:52
@lurtz
lurtz changed the base branch from improved-caching to main July 17, 2026 10:53
@lurtz lurtz changed the title use cicd-actions part-2 branch feat: Improve bazel caching Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants