[JIRA] (JENKINS-40847) JNLP slave pod gets created even when a different slave is configured

[lars.law...@gmail.com (JIRA)]

Title: Message Title

Lars Lawoko commented on JENKINS-40847   Re: JNLP slave pod gets created even when a different slave is configured We had the same problem; either name your container 'jnlp' as a hack, or do a container step container('<name>') { //code } relevent code: https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java if (!containers.containsKey(JNLP_NAME)) { ContainerTemplate containerTemplate = new ContainerTemplate(DEFAULT_JNLP_IMAGE); containerTemplate.setName(JNLP_NAME); containerTemplate.setArgs(DEFAULT_JNLP_ARGUMENTS); containers.put(JNLP_NAME, createContainer(slave, containerTemplate, template.getEnvVars(), volumeMounts.values())); } 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.