[JIRA] (JENKINS-60408) Workspace Volume configuration not being used

[neil.r.green+jenk...@gmail.com (JIRA)]

Title: Message Title

Neil Green created an issue   Jenkins / JENKINS-60408 Workspace Volume configuration not being used Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-12-09 17:36 Environment: Jenkins ver. 2.190.3 Kubernetes Plugin 1.21.4 Kubernetes 1.14.8-eks Priority: Major Reporter: Neil Green I have configured a Dynamic PVC Workspace volume through the jenkins ui. It's not being picked up by the build pods from a Jenkins declarative pipeline. I've checked what's in config.xml and this block has been created: {{}} <workspaceVolume class="org.csanchez.jenkins.plugins.kubernetes.volumes.workspace.DynamicPVCWorkspaceVolume"> <storageClassName>gp2</storageClassName> <requestsSize>30Gi</requestsSize> <accessModes>ReadWriteOnce</accessModes> </workspaceVolume> {{}} The storage class gp2 exists in the cluster and its provisioner is kubernetes.io/aws-ebs. It has been used to provision other For debugging purposes, I've tried different workspace volume settings, including different classes (e.g. NFS, Host Path), but none of them have any effect. Regardless of the configuration the build always outputs: {{}} volumes:   - configMap:       name: "qb-build-m2"     name: "m2"   - emptyDir:       medium: ""     name: "workspace-volume"   The configMap volume comes from the Jenkinsfile   Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203465.1575912972000.3110.1575913020113%40Atlassian.JIRA.