[JIRA] (JENKINS-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title
Lars Lawoko edited a comment on JENKINS-40825
Re: "Pipe not connected" errors when running multiple builds simultaneously
Esentially the bug is in the "container" step, so if you avoid it this bug should be worked around. Of course if you rely on shared disk of one pod with multiple containers this won't workInstead of having {code:java} podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'debian', image: 'debian', ttyEnabled: true, command: 'cat')]) \{ node('mypod') \{container('debian') \{ stage('stage 1') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' } stage('stage 2') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' }} }} {code} (pusdocode, might need more tweaking)have: ( note the new image,the name is jnlp ( See https://issues.jenkins-ci.org/browse/JENKINS-40847), and no contianer step) {code:java} podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'jnlp', image: 'custom/debian-with-jnlp'),]) \{ node('mypod') \{ stage('stage 1') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' } stage('stage 2') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' } }} {code} Not at work now, but If someone needs a more indepth walkthrough, comment here.
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
[JIRA] (JENKINS-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title
Lars Lawoko commented on JENKINS-40825
Re: "Pipe not connected" errors when running multiple builds simultaneously
Esentially the bug is in the "container" step, so if you avoid it this bug should be worked around. Of course if you rely on shared disk of one pod with multiple containers this won't work Instead of having podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'debian', image: 'debian', ttyEnabled: true, command: 'cat') ]) { node('mypod') { container('debian') { stage('stage 1') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } stage('stage 2') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } } } } (pusdocode, might need more tweaking) have: ( note the new image,the name is jnlp ( See https://issues.jenkins-ci.org/browse/JENKINS-40847), and no contianer step) podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'jnlp', image: 'custom/debian-with-jnlp'), ]) { node('mypod') { stage('stage 1') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } stage('stage 2') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } } } Not at work now, but If someone needs a more indepth walkthrough, comment here.
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-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title Lars Lawoko commented on JENKINS-40825 Re: "Pipe not connected" errors when running multiple builds simultaneously We have been having this issue, and did an investigation. It seems to be failing on pipe write in the first "cd" command to get the workspace. From what we understand the underlying kubernetes-client library does not expose a stable connection. From what we understand the latch was implemented wrongly (?? We think). The latch is initialized once in the `container` "start" method, but a new connection is opened for each `sh` step. This causes the "waitQuietly" to pass through straight away without waiting, on all sh connections but the first. Once we fixed this the "OnOpen" callback in the websocket is never called, indicating the connection is not made, and the latch was only passed on thread interrupt. At this stage we didn't dig deeper, but hopefully this is a good starting point. Instead we switched to embedding jnlp into our main container using the "jnlp" container name "hack" to workaround this code. TL;DR Embedding jnlp into your main container using the "jnlp" container name "hack" will workaround this issue code. 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-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title Lars Lawoko commented on JENKINS-40825 Re: "Pipe not connected" errors when running multiple builds simultaneously Still happening for us. could be related to "java.io.Piped*Stream are not threads friendly and cause 'Pipe is broken' issue when jenkins pool the writing threads"? https://issues.jenkins-ci.org/browse/JENKINS-23958?focusedCommentId=228900=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-228900 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko edited a comment on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException [~iocanel] Will do, i believe [~jglick] is part of that plugin team?Also if you are in the kubernetes team and have time, could you have a quick look at JENKINS- 42048 40647 , I can confirm that it is still happening with the plugins updated to latest. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Ioannis Canellos Will do, i believe Jesse Glick is part of that plugin team? Also if you are in the kubernetes team and have time, could you have a quick look at JENKINS-42048 , I can confirm that it is still happening with the plugins updated to latest. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko assigned an issue to Jesse Glick Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Lars Lawoko Assignee: Ioannis Canellos Jesse Glick 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko edited a comment on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException [~daichirata] Thanks, just tried this and can confirm that Pipeline Nodes and Processes Plugin 2.9 is the issue [~iocanel] He narrowed it down to this plugin / version 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Daichi Hirata Thanks, just tried this and can confirm that Pipeline Nodes and Processes Plugin 2.9 is the issue 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko updated an issue Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Lars Lawoko Component/s: workflow-durable-task-step-plugin 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Lars Lawoko edited a comment on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
For more context we are running on the Google container engine (hosted k8), The weird thing is that it seems to be working right, i.e the pipeline builds, even with the constant exception.The exception starts once the gradle shell is run:{code}[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build & run unit tests)[Pipeline] withEnv[Pipeline] {[Pipeline] sh00:01:05.567 [Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A] Running shell script00:01:05.572 Executing shell script inside container [gcloud-jdk7] of pod [kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9]00:01:05.653 Executing command: sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt' 00:01:05.694 # cd /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A00:01:05.694 sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6E# PNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt' 00:01:05.694 exit00:01:05.909 + ./gradlew --stacktrace --parallel buildUnitTest00:01:05.909 Downloading https://services.gradle.org/distributions/gradle-3.3-all.zip00:01:05.995 Cannot contact kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid: java.lang.NumberFormatException: For input string: ""{code}Our jenkinsfile is pretty massive, but here is the core (has been edited):{code} podTemplate(label: 'JavaPod', containers: [containerTemplate(name: 'gcloud-jdk7',image: 'gcr.io/pc-infrastructure/robusta-jenkins-gcloud-jdk7',ttyEnabled: true,args: 'cat',command: '/bin/sh -c',alwaysPullImage: true,workingDir: '/home/jenkins',resourceRequestCpu: '2',resourceRequestMemory: '8Gi',resourceLimitCpu: '5',resourceLimitMemory: '9Gi',),containerTemplate(name: 'jnlp',image: 'jenkinsci/jnlp-slave:alpine',args: '${computer.jnlpmac} ${computer.name}',resourceRequestCpu: '100m',resourceRequestMemory: '500Mi',resourceLimitCpu: '500m',resourceLimitMemory: '1Gi',)]) { node('JavaPod') {container('gcloud-jdk7') {timeout(30) {
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Lars Lawoko commented on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
For more context we are running on the Google container engine (hosted k8), The weird thing is that it seems to be working right, i.e the pipeline builds, even with the constant exception. The exception starts once the gradle shell is run:
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build & run unit tests)
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
00:01:05.567 [Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A] Running shell script
00:01:05.572 Executing shell script inside container [gcloud-jdk7] of pod [kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9]
00:01:05.653 Executing command: sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt'
00:01:05.694 # cd /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A
00:01:05.694 sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6E# PNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt'
00:01:05.694 exit
00:01:05.909 + ./gradlew --stacktrace --parallel buildUnitTest
00:01:05.909 Downloading https://services.gradle.org/distributions/gradle-3.3-all.zip
00:01:05.995 Cannot contact kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid: java.lang.NumberFormatException: For input string: ""
Our jenkinsfile is pretty massive, but here is the core (has been edited):
node('JavaPod') {
container('gcloud-jdk7') {
timeout(30) { //assume something is wrong if it takes an half an hour
stage('checkout source') {
checkout scm
}
switch (env.BRANCH_NAME) {
case 'develop':
buildUnitTest()
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko created an issue Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Issue Type: Bug Assignee: Ioannis Canellos Components: kubernetes-pipeline-plugin, workflow-api-plugin Created: 2017/Feb/15 5:03 AM Environment: Jenkins 2.32.2 Priority: Minor Reporter: Lars Lawoko I tried to narrow this bug down, but there isn't much information. We just upgraded to all newest plugins, but unfortunately we upgraded a lot at once, so no idea which one. This is spamming out logs every few seconds: 00:19:42.695 Cannot contact kubernetes-ef39fe82c8a541be84bd780e4d7c1ddb-ce4d47fc96bfc: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-96fa79b7/pid: java.lang.NumberFormatException: For input string: "" 00:19:57.758 Cannot contact kubernetes-ef39fe82c8a541be84bd780e4d7c1ddb-ce4d47fc96bfc: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-96fa79b7/pid: java.lang.NumberFormatException: For input string: "" 00:20:12.769 Cannot contact kubernetes-ef39fe82c8a541be84bd780e4d7c1ddb-ce4d47fc96bfc: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-96fa79b7/pid: java.lang.NumberFormatException: For input string: ""
[JIRA] (JENKINS-39346) Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline
Title: Message Title Lars Lawoko updated an issue Jenkins / JENKINS-39346 Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline Change By: Lars Lawoko Environment: Jenkins 2. 7.3 45 Pipeline 2. 4 10 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-39346) Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline
Title: Message Title Lars Lawoko reopened an issue The "workflow-api" plugin which contains the "duplicate" fix has been fixed since 2.5; "2.5 (Oct 19, 2016) JENKINS-34488 Various errors when trying to run assert statements, and under certain other conditions as well." We can confirm that as of version 2.8, Jenkins LTS today, this issue still occurs. I will try to re-open this issue? Sorry if that is premature. Jenkins / JENKINS-39346 Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline Change By: Lars Lawoko Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39346) Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline
Title: Message Title Lars Lawoko commented on JENKINS-39346 Re: Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline The "workflow-api" plugin which contains the "duplicate" fix has been fixed since 2.5; "2.5 (Oct 19, 2016) JENKINS-34488 Various errors when trying to run assert statements, and under certain other conditions as well." We can confirm that as of version 2.8, Jenkins LTS today, this issue still occurs. I will try to re-open this issue? Sorry if that is premature. 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-40647) With Env not working after .10 k8 plugin update
Title: Message Title Lars Lawoko commented on JENKINS-40647 Re: With Env not working after .10 k8 plugin update Can we confirm that this is a bug with the plugin, and not our setup? It requires ugly workarounds in its present state. 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-40847) JNLP slave pod gets created even when a different slave is configured
Title: Message Title Lars Lawoko edited a comment on JENKINS-40847 Re: JNLP slave pod gets created even when a different slave is configured Note that We have had a problem with WithEnv block inside a container block, issue JENKINS- 40838 40647 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-40847) JNLP slave pod gets created even when a different slave is configured
Title: Message Title Lars Lawoko commented on JENKINS-40847 Re: JNLP slave pod gets created even when a different slave is configured Note that We have had a problem with WithEnv block inside a container block, issue JENKINS-40838 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-40847) JNLP slave pod gets created even when a different slave is configured
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('') {
//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
[JIRA] (JENKINS-40647) With Env not working after .10 k8 plugin update
Title: Message Title
Lars Lawoko commented on JENKINS-40647
Re: With Env not working after .10 k8 plugin update
Following up, can confirm it is a problem with the container step, The first printenv is correctly populated, but the second is not
node('JavaPod') {
withEnv(runEnv) {
sh 'printenv'
}
container('gcloud-jdk7') {
withEnv(runEnv) {
sh 'printenv'
}
}
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-39346) Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline
Title: Message Title Lars Lawoko commented on JENKINS-39346 Re: Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline Same issue for us with sonarqube 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-40647) With Env not working after .10 k8 plugin update
Title: Message Title
Lars Lawoko edited a comment on JENKINS-40647
Re: With Env not working after .10 k8 plugin update
{code: groovy java }runEnv = []runEnv.add('JAVA_OPTS=-Xmx6g')runEnv.add('npm_config_registry=http://nexus.default.svc.cluster.local:8081/repository/npm/')withEnv(runEnv) { try { sh './gradlew --stacktrace --parallel jenkinsBuild' } catch (Exception e) { junit allowEmptyResults: true, testResults: '**/build/test-results/**/*.xml' step([$class: 'CheckStylePublisher', canComputeNew: false, defaultEncoding: '', healthy: '', pattern: '**/main.xml,**/test.xml', unHealthy: '']) throw e }{code}Adding a {code: groovy java }sh 'printenv'{code}Shows the env is not populatedP.s it is inside a container which contains JDK 7 & gcloud{code: :groovy java } node('JavaPod') {container('gcloud-jdk7') {{code}
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-40647) With Env not working after .10 k8 plugin update
Title: Message Title
Lars Lawoko commented on JENKINS-40647
Re: With Env not working after .10 k8 plugin update
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
runEnv = []
runEnv.add('JAVA_OPTS=-Xmx6g')
runEnv.add('npm_config_registry=http://nexus.default.svc.cluster.local:8081/repository/npm/')
withEnv(runEnv) {
try {
sh './gradlew --stacktrace --parallel jenkinsBuild'
} catch (Exception e) {
junit allowEmptyResults: true, testResults: '**/build/test-results/**/*.xml'
step([$class: 'CheckStylePublisher', canComputeNew: false, defaultEncoding: '', healthy: '', pattern: '**/main.xml,**/test.xml', unHealthy: ''])
throw e
}
Adding a
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
sh 'printenv'
Shows the env is not populated P.s it is inside a container which contains JDK 7 & gcloud
Unable to find source-code formatter for language: :groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
node('JavaPod') {
container('gcloud-jdk7') {
[JIRA] (JENKINS-40647) With Env not working after .10 k8 plugin update
Title: Message Title
Lars Lawoko created an issue
Jenkins / JENKINS-40647
With Env not working after .10 k8 plugin update
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2016/Dec/23 12:07 AM
Priority:
Minor
Reporter:
Lars Lawoko
WithEnv inside a container('x'){} is not working for us, when I did sh 'printenv' none of the variables were in the ENV.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
