[
https://issues.apache.org/jira/browse/FLINK-40124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Nuyanzin updated FLINK-40124:
------------------------------------
Fix Version/s: 2.3.1
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.1, 2.4.0
>
>
> {{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/apache/flink/actions/runs/29151024404/job/86624082702
> look for {{Cache saved with key}}, there is a record like
> {quote}
> 2026-07-12T06:50:20.5791878Z Cache saved with key:
> Linux-ns-master-maven-f40eab2dd53e0a6db3276e1ae336e29102ccff62b2aa106a84eea1185d70a09c-29151024404
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
