[JIRA] (JENKINS-57574) NO_PROXY enviroment overwritten with side value on slave/JNLP

[kichay.d@gmail.com (JIRA)]

Danil Kichay updated an issue

Jenkins / JENKINS-57574 NO_PROXY enviroment overwritten with side value on slave/JNLP Change By: Danil Kichay Summary: NO_PROXY enviroment overwrites overwritten with side value on slave/JNLP Add Comment

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

[kichay.d@gmail.com (JIRA)]

Danil Kichay updated an issue

Jenkins / JENKINS-57574 NO_PROXY enviroment overwritten with side value on slave/JNLP Change By: Danil Kichay

[https://hub.docker.com/r/openshift/jenkins-2-centos7] updated jenkins war /usr/lib/jenkins/jenkins.war 2.164.3 updated all plugins Kubernetes plugin 1.15.4 I have a kubernetes cloud plugin with kubernetes pod template configurated. There are HTTP_PROXY, HTTPS_PROXY, NO_PROXY variables is set with "Raw yaml for the Pod" in template configuration. I have a NO_PROXY with "jenkins," value overwriten but not added to the variable. This behavior breaks pipelines with proxy-through routing to a local services with any NO_PROXY configuration in templates. It worked works good on old Jenkins 2.138.2 with Kubernetes plugin 1.12.8. I suspected that NO_PROXY enviroment has been overwriten with "Jenkins URL" hostname from configuration when slave nodes running. Sorry for my poor grammar.

Add Comment

[kichay.d@gmail.com (JIRA)]

Danil Kichay updated an issue

Jenkins / JENKINS-57574 NO_PROXY enviroment overwritten with side value on slave/JNLP Change By: Danil Kichay

[https://hub.docker.com/r/openshift/jenkins-2-centos7] updated jenkins war /usr/lib/jenkins/jenkins.war 2.164.3 updated all plugins Kubernetes plugin 1.15.4

I have a kubernetes cloud plugin with kubernetes pod template configurated. There are HTTP_PROXY, HTTPS_PROXY, NO_PROXY variables is set with "Raw yaml for the Pod" in template configuration. I have a NO_PROXY with "jenkins," value overwriten but not added appended ("jenkins,172.30.0.0/16,.local.test.domain...") to the variable. This behavior breaks pipelines with proxy-through routing to a local services with any NO_PROXY configuration in templates. It works good on old Jenkins 2.138.2 with Kubernetes plugin 1.12.8.

I suspected that NO_PROXY enviroment has been overwriten with "Jenkins URL" hostname from configuration when slave nodes running. Sorry for my poor grammar.

Add Comment