[JIRA] (JENKINS-56029) Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Title: Message Title
James Nelson commented on JENKINS-56029
Re: Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Curious if there's any more details on this? We're seeing a similar issue. Are you using `node(POD_LABEL)` or just going straight to `container('containerName')`?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.197449.1549559392000.4287.1564506420258%40Atlassian.JIRA.
[JIRA] (JENKINS-56029) Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Title: Message Title Martin Sjölund commented on JENKINS-56029 Re: Kubernetes Plugin: Concurrent builds do not have their own unique workspaces I have similar issues where two parallel jobs in a pipeline each execute on a different pod on the same machine. They both try to do git pull at the same time, causing conflicts in the index.lock files, etc. I would be perfectly happy with something like #47591 or simply having the possibility to not use persistent storage at all for my pod (slower, but at least would not break things and is probably easy to implement). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56029) Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Title: Message Title Amrit Gill updated an issue Jenkins / JENKINS-56029 Kubernetes Plugin: Concurrent builds do not have their own unique workspaces Change By: Amrit Gill Cluster Version: 1.10Plugin Version: 1.13.5Jenkins Version: 2.159 I am using the kubernetes plugin to dynamically create slaves on a k8s cluster.When there are concurrent builds are running of a specific job, they are both using the same workspace which causes all sorts of issues. For example, if I have some cleanUp in my Jenkinsfile, and there are 2 concurrent builds running, if the build 1 finishes first and runs cleanWs(), it deletes everything from that Workspace. Since build 2 is also using the same workspace, build 2 also fails because it lost everything in its workspace ( because they were both using the same workspace ). This behavior is not correct and it should match the native jenkins behavior when using static slaves. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56029) Kubernetes Plugin: Concurrent builds do not have their own unique workspaces
Title: Message Title Amrit Gill created an issue Jenkins / JENKINS-56029 Kubernetes Plugin: Concurrent builds do not have their own unique workspaces Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-02-07 17:09 Priority: Blocker Reporter: Amrit Gill I am using the kubernetes plugin to dynamically create slaves on a k8s cluster. When there are concurrent builds are running of a specific job, they are both using the same workspace which causes all sorts of issues. For example, if I have some cleanUp in my Jenkinsfile, and there are 2 concurrent builds running, if the build 1 finishes first and runs cleanWs(), it deletes everything from that Workspace. Since build 2 is also using the same workspace, build 2 also fails because it lost everything in its workspace ( because they were both using the same workspace ). This behavior is not correct and it should match the native jenkins behavior when using static slaves. Add Comment
