[JIRA] (JENKINS-52978) Improve image definition of jnlp container
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-52978 Improve image definition of jnlp container 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.192959.1533893158000.13129.1563306227543%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52978) Improve image definition of jnlp container
Title: Message Title Jochen Niebuhr created an issue Jenkins / JENKINS-52978 Improve image definition of jnlp container Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-08-10 09:25 Priority: Minor Reporter: Jochen Niebuhr The default for the autogenerated JNLP container is to have it's image set to "jenkins/jnlp-slave:alpine" and the imagePullPolicy set to "IfNotExists". After some updates this might lead to very old cached versions of the image "jenkins/jnlp-slave:alpine" which might not work with the Jenkins itself anymore. This could be resolved by: a) Setting the jnlp version to a compatible version on every new kubernetes plugin release (i.E. jenkins/jnlp-slave:3.23-1-alpine) b) Setting the imagePullPolicy to Always (This might annoy some people because it will do unnecessary requests) I've solved the problem for myself by creating a default pod template with the current jnlp-slave but that seems a bit like a workaround to me. Add Comment
