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

0 views
Skip to first unread message

neil.r.green+jenkins@gmail.com (JIRA)

unread,
Dec 9, 2019, 12:37:03 PM12/9/19
to jenkinsc...@googlegroups.com
Neil Green created an issue
 
Jenkins / Bug JENKINS-60408
Workspace Volume configuration not being used
Issue Type: Bug 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 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 Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

vincent@latombe.net (JIRA)

unread,
Jan 24, 2020, 10:10:02 AM1/24/20
to jenkinsc...@googlegroups.com
Vincent Latombe commented on Bug JENKINS-60408
 
Re: Workspace Volume configuration not being used

Can't reproduce (1.23.1). Please make sure the pod template that is used for your build is indeed the one where you defined the dynamic PVC.

vincent@latombe.net (JIRA)

unread,
Jan 24, 2020, 10:10:03 AM1/24/20
to jenkinsc...@googlegroups.com
Vincent Latombe closed an issue as Cannot Reproduce
 
Change By: Vincent Latombe
Status: Open Closed
Resolution: Cannot Reproduce

david.warburton@gmail.com (JIRA)

unread,
May 5, 2020, 10:43:04 AM5/5/20
to jenkinsc...@googlegroups.com

Please make sure the pod template that is used for your build is indeed the one where you defined the dynamic PVC.

Vincent Latombe what was the declarative pipeline definition you used to prove this works? I can't find one.

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

david.warburton@gmail.com (JIRA)

unread,
May 5, 2020, 10:45:02 AM5/5/20
to jenkinsc...@googlegroups.com
david warburton edited a comment on Bug JENKINS-60408
{quote} Please make sure the pod template that is used for your build is indeed the one where you defined the dynamic PVC Can't reproduce (1 . 23.1).
{quote}
[~vlatombe] what was the declarative pipeline definition you used to prove this works? I can't find one.
Reply all
Reply to author
Forward
0 new messages