[JIRA] (JENKINS-40805) Workspace not available when a slave is created by the Kubernetes plugin

[olivier.lambert@smals.be (JIRA)]

Olivier Lambert created an issue

Jenkins / JENKINS-40805 Workspace not available when a slave is created by the Kubernetes plugin Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Jan/04 3:06 PM Priority: Major Reporter: Olivier Lambert I'm configuring an environment with a jenkins master that uses kubernetes to instantiate slaves. Everyting works fine except that the workspace is not available when the slave is killed by the kubernetes (slave offline). I have tried several solutions (using an NFS, copying back the workspace on the master with the copy-to-slave plugin, ... aso) .... but it doesn't work ... Jenkins don't want to display the workspace if the node is offline (even if the workspace is at the right location, but on the master). Do you have a solution ? Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[pallikon@gmail.com (JIRA)]

Raghu Pallikonda commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin Carlos Sanchez Could you please help with this issue, or how we can fix it? Olivier Lambert Could you please let me know if you were able to solve the issue? We do have a workaround which is not that nice.. Once the build is done, we have to change the 'where the project is run ' to master. Then the workspace is shown.

Add Comment

[olivier.lambert@smals.be (JIRA)]

Olivier Lambert commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

Raghu Pallikonda We also find this workaround. It works fine .... but it's just a workaround ... We think a better solution should be implemented directlry in the core of Jenkins. 1. Check if the "where the project is run" is online 2. IF YES >> display this workspace 3. IF NO >> check if it's available on the master 4. IF YES, display it 5. IF NO, display error message

Add Comment

[jbounds83@gmail.com (JIRA)]

Jereme Bounds commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

Olivier Lambert, looks like this PR was never approved. How did you get around this issue? Carlos Sanchez We have the same exact issue. Looks like the PR was never approved. Can we submit a new PR for this?

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[jenkins-ci@carlossanchez.eu (JIRA)]

Carlos Sanchez commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

You can continue with the existing PR it was never completed

Add Comment

[jbounds83@gmail.com (JIRA)]

Jereme Bounds commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

Awesome. Thanks Carlos Sanchez.

Add Comment

[fadi.farah@covisint.com (JIRA)]

Fadi Farah commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

Carlos Sanchez, using copy-to-slave plugin is a terrible idea. Because that plugin isn't maintained and is even taken off of the official Jenkins plugin list due to unfixed security problems. Being able to view the workspace after the slave node is destroyed is quite important and would be very useful to have that feature built in.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[tdihp@hotmail.com (JIRA)]

Ping He commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

It seems post-build actions in freestyle build, that uses workspace, such as S3 Publisher, will also fail trying to connect to the pod by JNLP.

Add Comment

[syaramada-c@scrippsnetworks.com (JIRA)]

suryatej yaramada commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

May be we use of https://github.com/jenkinsci/external-workspace-manager-plugin/blob/master/README.md this plugin to get view the workspace form GUI if some configurations changes happen in both kubernetes plugin and as well Jenkins

Add Comment

[syaramada-c@scrippsnetworks.com (JIRA)]

suryatej yaramada commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin

Can I know if any one able to solve this issue??

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick assigned an issue to Unassigned

Jenkins / JENKINS-40805

Workspace not available when a slave is created by the Kubernetes plugin

Change By: Jesse Glick Assignee: Carlos Sanchez

Add Comment

[narayananalagesigari@gmail.com (JIRA)]

Narayana Nalagesigari commented on JENKINS-40805

Re: Workspace not available when a slave is created by the Kubernetes plugin I am also facing the issue where we would like to see the job's workspace after the pod terminated . Our agents are attached to a PVC ( persistence volume ) and can still see the workspace even after the pod terminates but cannot access through the job bcz no pod exist.  please let me know if you found ways to address this issue

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)