FFFF
Skip to content

CI: evaluate safe caching of V build artifacts #27844

Description

@ulises-jeremias

Describe the feature

Evaluate safe caching or reuse of the V compiler build artifact across GitHub Actions jobs.

Use Case

Many workflows rebuild V from scratch with make, make -j4, make && ./v symlink, or Windows makev.bat. This happens independently across many jobs and matrices.

Rebuilding V is expected in a compiler repository, but repeated identical builds across workflows and matrix jobs add up.

Proposed Solution

Experiment with opt-in build artifact caching in a low-risk workflow first.

Possible key:

key: v-build-${{ runner.os }}-${{ matrix.cc || 'default' }}-${{ hashFiles('cmd/**', 'vlib/**', 'thirdparty/**', 'make*') }}

Possible cached paths:

path: |
  v
  v.exe
  cmd/tools/builders

Start with a small workflow where stale compiler risk is low, then expand if reliable.

Other Information

Caution: compiler projects can be sensitive to stale binaries. The cache key must include all relevant source/build inputs. It may be safer to implement this after a shared setup action exists.

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

Version used

master as of 2026-07-18.

Environment details (OS name and version, etc.)

GitHub Actions workflow analysis using GitHub CLI from Linux.

Metadata

Metadata

Labels

BuildV build error on any OS/CPU architecture.Feature/Enhancement RequestThis issue is made to request a feature or an enhancement to an existing one.Unit: ToolingBugs/feature requests, that are related to the tooling for the language.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

0