[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title
david warburton edited a comment on JENKINS-60408
Re: Workspace Volume configuration not being used
{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.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.22033.1588689900156%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title david warburton commented on JENKINS-60408 Re: Workspace Volume configuration not being used 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. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.22030.1588689780266%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title Vincent Latombe commented on 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. 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.5115.1579878600460%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title Vincent Latombe closed an issue as Cannot Reproduce Jenkins / JENKINS-60408 Workspace Volume configuration not being used Change By: Vincent Latombe Status: Open Closed Resolution: Cannot Reproduce 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.5118.1579878600584%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
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: {{}}
"org.csanchez.jenkins.plugins.kubernetes.volumes.workspace.DynamicPVCWorkspaceVolume">
gp2
30Gi
ReadWriteOnce
{{}} 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
