[JIRA] (JENKINS-42763) Env var HOME for containers has regressed

[parag.doke+tec...@gmail.com (JIRA)]

Title: Message Title

Parag Doke created an issue   Jenkins / JENKINS-42763 Env var HOME for containers has regressed Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Mar/14 5:34 PM Environment: Jenkins ver. 2.7.21.0.1 (CloudBees Jenkins Enterprise 2.7.21.0.1-fixed) Kubernetes plugin version 0.9 Priority: Major Reporter: Parag Doke Since version 0.7 of kubernetes-plugin, due to PR https://github.com/jenkinsci/kubernetes-plugin/pull/57, a change was made that I think is specific to some kubernetes cloud environments (openshift), but not all. For instance, I have a Jenkins instances connected to a kubernetes cluster, and don't want HOME to be set to working directory.   I also saw https://github.com/jenkinsci/kubernetes-plugin/pull/128 that attempted to address some points, but (correct me if I am wrong), we'd still need to set HOME on each pod template.   I think a better way of fixing the problem would be to introduce a checkbox on the cloud config level ... that says something to the effect of "Ensure functional HOME folder" (to begin with). Such a param would remove the need for each pod template to be configured ... and yet allow Jenkins admin(s) to get the desired effect in case of openshift.   Needless to say, this would be conditional: env.put("HOME", containerTemplate.getWorkingDir()); 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.