Affected tool: spacemedia
I tried to do
After a successful first build (spacemedia-buildpacks-pipelinerun-56fz5) that took 7 minutes, I tried to start a new one to check that the next builds are faster.
As per documentation the .m2 folder (local maven repository) should be cached between builds, so the new build shouldn't spend ~6 minutes to download all dependencies again.
And this happened
The new build (spacemedia-buildpacks-pipelinerun-b4p75) redownloaded all dependencies and spent 7 minutes again:
Build ID: spacemedia-buildpacks-pipelinerun-b4p75 Start Time: 2023-11-01T20:14:54Z End Time: 2023-11-01T20:21:42Z Status: ok Message: Tasks Completed: 1 (Failed: 0, Cancelled 0), Skipped: 0 Parameters: Source URL: https://gitlab.wikimedia.org/toolforge-repos/spacemedia Ref: N/A Destination Image: tools-harbor.wmcloud.org/tool-spacemedia/tool-spacemedia:latest
But I was expecting
Previously downloaded Maven artifacts should not be downloaded again, and the build time should have been around 1 minute max.