On master (502d22ceed1f90ed41336260f8eb428d3acaf514) the Cirrus CI do not invalidate depends caches when their sources has been changed, i.e. source version updates, a new dependency etc.
This behavior causes:
- breaking CI build for Android APK (see #22708)
- the cache sizes growing
It is assumed that caches could be invalidated via Cirrus CI API/GUI, but it is inconvenient and it does not work as expected in all cases.
The common part of fingerprint_key
s for both depends_sources_cache
and depends_built_cache
is the recent commit that changes sources in the src/depends
sub-directory.
For depends_built_cache
additionally CIRRUS_TASK_NAME
is used to avoid sharing of the same cache between tasks with different OSes and different DEP_OPTS
.
The depends_sources
cache:
- in master (502d22ceed1f90ed41336260f8eb428d3acaf514)
- with this PR