Skip to content

CI: cache the Julia depot - #149

Merged
mathieu17g merged 1 commit into
mainfrom
ci-julia-cache
Sep 11, 2026
Merged

mathieu17g merged 1 commit into
mainfrom
ci-julia-cache

Conversation

@mathieu17g

Copy link
Copy Markdown
Collaborator

The [julia-buildpkg] notice on every job says it: no depot cache is restored. The workflow's only Julia cache keyed on ~/.julia/artifacts, a directory this package never creates, so it never hit and never saved.

julia-actions/cache@v3 replaces it in both CI jobs and is added to Downstream: registries, packages and compiled code are restored per job and matrix cell, and the previous cache of the key is deleted, which needs actions: write on the token.

On the last run of main, the work this can save per job is the test-dependency and coverage-tool precompilation plus buildpkg: about 15 s on Linux and 40 s on the Intel macOS runner. Downstream installs XLSX and SatelliteToolboxOrbitDataMessages with their dependencies on every run and should gain more.

The artifacts cache never hit: XML.jl has no artifact, so the directory
it keyed on never existed and nothing was saved. julia-actions/cache
restores and saves the whole depot, registries, packages and compiled
code included, one key per job and matrix cell, and deletes the
previous cache of that key. Downstream, which installs two dependents
per job, gets the same step.

Assisted-by: Claude (Anthropic)
@mathieu17g
mathieu17g marked this pull request as ready for review September 11, 2026 21:49
@mathieu17g
mathieu17g merged commit a78327e into main Sep 11, 2026
13 checks passed
@mathieu17g
mathieu17g deleted the ci-julia-cache branch September 11, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant