Sergey Nuyanzin created FLINK-40124:
---------------------------------------
Summary: Maven package cache in job_init action re-saves on every
CI run instead of only when dependencies change
Key: FLINK-40124
URL: https://issues.apache.org/jira/browse/FLINK-40124
Project: Flink
Issue Type: Sub-task
Components: Build System / CI
Reporter: Sergey Nuyanzin
Assignee: Sergey Nuyanzin
{{job_init/action.yml}}'s Maven cache key includes ${{ github.run_id }}, unique
per run, so the primary key can never match a previous run — cache-hit is
always false. restore-keys still restores correctly (confirmed via logs), but
the save step then unconditionally re-uploads the full .m2 cache every run,
even with unchanged pom.xml.
could be checked by looking into GHA logs for instance
https://github.com/snuyanzin/flink/actions/runs/29182164397/job/86621779423
look for {{Cache saved with key}}, there is a record like
{quote}
Cache saved with key:
Linux-ns-master-maven-03e1d3903ca1f296622d48f2fd63d6e995e49bafd35997661a78ece0ee0b726f-29098781213
{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)