Hi, our company recently adopt an OpenShift. We are moving the whole build infrastructure (agents provisioning but not master) on this cloud using the kubernates plugin.

After long search I plan to implement a different WorkspaceVolume than dynamicPVC that does not remove the persistent volume after the pod has been  deleted.

What I would is that untill a job is in place I will gain the caching of the persistence (pvc) to avoid download whole GIT repository, tools, maven repo and/or npm repo and/or ruby gems for each build. With multibranch projects PRs jobs will be boosted.

Implementing a ItemListener the PVC could be deleted when the job go away.

Actually on the kubernetes cloud settings is not possible use enviroment variable like JOB_NAME because are not resolved. A "Per Job PVC workspace volume" strategy should not take the name but generate it from the job name. At the time of writing the WorkspaceVolume method are tailored for the dynamicPVC and there are not other chance to get other information about the job.

I would propose a PR to pass additional informations to the WorkspaceVolume implementations and allow customisations.