The artefacts downloaded are not cached when we issue a second build using a PipelineRun where a volume is mounted using a pvClaimTemplate
Every time we execute a Tekton PipelineRun, the task running the lifecycle re-download by example the following JDK during the execution of the "bellsoft-liberica" buildpacks
[buildpacks : build] BellSoft Liberica JDK 17.0.8: Contributing to layer
[buildpacks : build] Downloading from https://github.com/bell-sw/Liberica/releases/download/17.0.8+7/bellsoft-jdk17.0.8+7-linux-amd64.tar.gz
We dont observe such a problem using the pack client
Issue
The artefacts downloaded are not cached when we issue a second build using a PipelineRun where a volume is mounted using a pvClaimTemplate
Every time we execute a Tekton PipelineRun, the task running the lifecycle re-download by example the following JDK during the execution of the "bellsoft-liberica" buildpacks
We dont observe such a problem using the pack client
Are we missing a specific volume to be mounted or cache ?
Snippet code of the Tekton buildpack build step