Hello ! we have the same issue what we would like is the same behavior as : https://docs.gitlab.com/ee/ci/caching/
I have seen this example : https://github.com/jenkinsci/kubernetes-plugin/blob/master/examples/maven-with-cache.groovy but if several jobs run in parallel I don't want them to modify the same volumes and I would like to not create volumes before the jobs I have seen the dynamic claim options for workspace but data are common for a run and not a job does it ? our idea currently is creating a volume claim with a name ${jobid} or {folderId} and set a K8S cron job that delete frequently but we don't find a way to set this by default (we tried in raw yaml option but it seems it only support kind : Pod) Regards Le mercredi 11 juillet 2018 09:48:23 UTC+2, Enguerrand A a écrit : > > The problem is that I would like to automate the installation of the PV or > PVC without needing to specify it in the Jenkinsfile but at least I can > automate the creation of PVC or PV for each job to avoid manual operation. > > I saw that automatically a PVC or PV could be mounted for the workspace > Jenkins, but it raises concerns if 2 build on the same job runs on the same > shared workspace (build can inflict another by removing files for example) > > Le mardi 10 juillet 2018 15:35:17 UTC+2, Carlos Sanchez a écrit : >> >> you can mount a PV or PVC but depending on what backend you use that will >> prevent concurrent executions >> >> On Tue, Jul 10, 2018 at 3:05 PM Enguerrand A < >> allamel.e...@thalesaleniaspace.com> wrote: >> >>> Hello everyone, >>> >>> I use the Kubernetes plugin for Jenkins to launch all Jenkins jobs in a >>> Kubernetes cluster. For better performance, I want to use a persistent >>> disk for the cache of different job Maven with insulation of it, ie a disk >>> space per job (to separate the cache) >>> >>> Do you have ideas for automatic solutions with the Kubernetes plugin to >>> have cache on the .m2 (or another type of cache) with a different disk by >>> jobs ? >>> >>> Thank you in advance ! >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-use...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/de71d26c-115e-4679-af8e-0151fbb3b8c9%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/de71d26c-115e-4679-af8e-0151fbb3b8c9%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/58617773-5901-4f03-97e3-4bfae081b207%40googlegroups.com.
