seems like there is an issue about it: https://issues.jenkins-ci.org/browse/JENKINS-42422
Le jeu. 26 mars 2020 à 08:07, Tristan FAURE <[email protected]> a écrit : > Hello > Thank you for the hint ! I think it could help some projects ! > but it will make some docker images very heavy and I would be interested > to have jenkins team opinion about getting the equivalent of > https://docs.gitlab.com/ee/ci/caching/ > > Le jeu. 26 mars 2020 à 06:10, Liejun Tao <[email protected]> a > écrit : > >> This is my solution for a little different purpose: use a .m2 cache for >> common libs. >> >> https://github.com/liejuntao001/jenkins-k8sagent-lib/blob/a6ced3975e37fe559c0ae8a918ed01b6920f1efa/resources/podtemplates/base.yaml#L24 >> The idea is to make a docker image with the most used artifacts(external >> dependencies) in .m2 folder. >> At the launch of the Agent, copy them to workspace's .m2 folder from the >> image. >> >> This should be adapted to fit your needs. >> I assume you are not going to run concurrent builds for a job to avoid >> concurrent write, if you want a job has a dedicated cache. >> At the end of a build, create a docker image based on the existing .m2 >> content and push back for next time use. >> >> If you are going to run concurrently builds, this idea of a sharing cache >> is invalid, I think. >> >> On Tue, Jul 10, 2018 at 8:05 AM Enguerrand A < >> [email protected]> 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 [email protected]. >>> 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. >>> >> >> >> -- >> Thanks, >> Baibai >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-users/X61BK83LHLU/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CAMRm5jbRhhtF5S4bzzT%3Du7La4sggNW2c-kEAjVMaqBeBK6cHPg%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAMRm5jbRhhtF5S4bzzT%3Du7La4sggNW2c-kEAjVMaqBeBK6cHPg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BtQ8YN41OAVo_u6kzGm5xiMxWHurVgpn%2BX3pGVZ18gjY%2B49cA%40mail.gmail.com.
