[JIRA] (JENKINS-36263) Kubernetes pod deleted before BuildWrapper cleanup
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-36263 Kubernetes pod deleted before BuildWrapper cleanup Change By: Jesse Glick Assignee: Carlos Sanchez 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.172270.1467104415000.13103.1563306226907%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36263) Kubernetes pod deleted before BuildWrapper cleanup
Title: Message Title Carlos Sanchez commented on JENKINS-36263 Re: Kubernetes pod deleted before BuildWrapper cleanup can you try with the latest version? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-36263) Kubernetes pod deleted before BuildWrapper cleanup
Title: Message Title Tomasz Wojtun commented on JENKINS-36263 Re: Kubernetes pod deleted before BuildWrapper cleanup Terminating a pod in a extension of hudson.model.listeners.RunListener on finalised event also can cause another RunListener to fail. Maybe keeping slave idle for customizable amount of time, before killing it is a good idea. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36263) Kubernetes pod deleted before BuildWrapper cleanup
Title: Message Title Tomasz Wojtun edited a comment on JENKINS-36263 Re: Kubernetes pod deleted before BuildWrapper cleanup I can confirm that OnceRetentionStrategy terminates the slave node before all of the publishers finish.Changing it to CloudRetentionStrategy helps, but it is not ideal as then slave can be reused by another build. kubernetes-plugin-0.8, jenkins 2.21 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36263) Kubernetes pod deleted before BuildWrapper cleanup
Title: Message Title Tomasz Wojtun commented on JENKINS-36263 Re: Kubernetes pod deleted before BuildWrapper cleanup I can confirm that OnceRetentionStrategy terminates the slave node before all of the publishers finish. Changing it to CloudRetentionStrategy helps, but it is not ideal as then slave can be reused by another build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36263) Kubernetes pod deleted before BuildWrapper cleanup
Title: Message Title David Joaquim created an issue Jenkins / JENKINS-36263 Kubernetes pod deleted before BuildWrapper cleanup Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Jun/28 9:00 AM Environment: Jenkins 2.3, kubernetes plugin 0.6, Cloudbees Docker Build environment Plugin 1.6.5 Priority: Critical Reporter: David Joaquim Hello, We use kubernetes plugin in conjunction with CloudBees Docker custom build environment Plugin. There is bad interaction between those plugins generating major resource leak. Indeed we discovered that the Kubernetes Pods are destroyed when the build completed but before build wrappers have a chance to tear down properly. This leads to resource leak on any build wrapper plugin that release its resource during tear down. In our specific case this mean all the docker containers launched by the custom environment plugin are never destroyed. We think that the problem is that KubernetesSlave relies on the OnceRetentionStrategy that terminates the slave node on the taskCompleted*() callback. This event seems to be before any hudson.tasks.BuildWrapper.Environment#tearDown(hudson.model.AbstractBuild, hudson.model.BuildListener) can be called. It was not clear for us how to solve this issue properly. Is there a way to extend hudson.model.listeners.RunListener and lookup/delete the pod from there ? Best Regards, David
