-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Jenkins ver. 2.190.3
Kubernetes Plugin 1.21.4
Kubernetes 1.14.8-eks
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