Re: [cbi-dev] emptyDir volume 'm2-repo'

[Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>]

It's only needed to trick Kubernetes. Without the empty dir, ~/.m2 is created because of 

volumeMounts:

      name: settings-xml

      mountPath: /home/jenkins/.m2/settings.xml

which makes it read-only. The trick to create an emptyDir is to make the ~/.m2/repository writable

Cheers,

Mikaël Barbero 

Team Lead - Release Engineering | Eclipse Foundation

📱 (+33) 642 028 039 | 🐦 @mikbarbero

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Le 8 juil. 2019 à 10:38, Karsten Thoms <karsten.thoms@xxxxxxxxx> a écrit :

In the wiki [1] it is recommended to declare a volume ‚m2-repo‘ and mounted to path '/home/jenkins/.m2/repository':
 - name: m2-repo
   emptyDir: {}
Could you explain please what is the sense behind using emptyDir here? Isn’t the agent starting always with an empty workspace?
Has this to do with volume space or performance?

~Karsten

[1] https://wiki.eclipse.org/Jenkins#Custom_container_on_Jiro
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cbi-dev

Attachment: signature.asc
Description: Message signed with OpenPGP