[JIRA] (JENKINS-46253) Support subPath for volumes in the slave PodTemplates

2 views
Skip to first unread message

danimajano@gmail.com (JIRA)

unread,
Feb 23, 2018, 6:09:02 AM2/23/18
to jenkinsc...@googlegroups.com
Daniel Majano commented on New Feature JENKINS-46253
 
Re: Support subPath for volumes in the slave PodTemplates

I'm facing to the same issue. It would be very top!

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

mathias.ahsberg@gmail.com (JIRA)

unread,
May 18, 2018, 9:37:03 AM5/18/18
to jenkinsc...@googlegroups.com

We are also facing this problem when we would like to mount an init.gradle file located in a ConfigMap to ${HOME}/.gradle/init.gradle.

The gradle wrapper will then not have access to the .gradle folder for writing.

If implementing support for subPath could solve our issue I am here to help.

jenkins-ci@carlossanchez.eu (JIRA)

unread,
May 18, 2018, 10:24:01 AM5/18/18
to jenkinsc...@googlegroups.com

jenkins-ci@carlossanchez.eu (JIRA)

unread,
May 25, 2018, 5:06:03 AM5/25/18
to jenkinsc...@googlegroups.com
Carlos Sanchez resolved as Won't Do
 
Jenkins / New Feature JENKINS-46253
Change By: Carlos Sanchez
Status: Open Resolved
Resolution: Won't Do

sxcoll2@yahoo.com (JIRA)

unread,
Sep 29, 2018, 3:35:02 PM9/29/18
to jenkinsc...@googlegroups.com
Steve Collins commented on New Feature JENKINS-46253
 
Re: Support subPath for volumes in the slave PodTemplates

though its possible with yaml syntax but isn't that only on a per job config basis.

If I have a number of caches I want to setup for all jobs (without changing each job to use a PodTemplate) and  I would like to do that using subpaths in the UI config, I don't see an option but I'm new to this so I may be missing something. 

 

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

eric.dejouhanet@smardtv.com (JIRA)

unread,
Oct 28, 2019, 1:56:03 PM10/28/19
to jenkinsc...@googlegroups.com

Although subPath can be managed by the PersistentVolumeClaim, it is not possible to use a different subPath in different pods as there is a 1:1 relation between PV and PVC.

In my situation, I have a single NFS storage, a "build cache", and I need to distribute that storage to multiple pods.

I don't want to assign the same build cache to all build pods, thus I need to partition the storage with sub-folders.

NFSVolume could be used with a different server path, but providing server information shortcuts what PVs are for.

PersistentVolumeClaim as it is now requires builds pods to create a subfolder themselves before storing their cache, or build jobs to state mountPath using pipeline, effectively duplicating the configuration in many places.

Anyone found a more elegant way to do this? Perhaps a PR modifying PodTemplateBuilder.build() would be acceptable?

 

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages