[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Pascal Laporte resolved as Fixed Jenkins / JENKINS-60831 Localisation to non-english is causing a lot of issues, bug and crashes Change By: Pascal Laporte Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204182.1579617297000.8188.1581523140628%40Atlassian.JIRA.
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Pascal Laporte commented on JENKINS-60831 Re: Localisation to non-english is causing a lot of issues, bug and crashes We have updated to 2.220 . Good news! Everything is now working in other language than English. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204182.1579617297000.8184.1581523080264%40Atlassian.JIRA.
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Pascal Laporte commented on JENKINS-60831 Re: Localisation to non-english is causing a lot of issues, bug and crashes Jon Brohauge It seem you have fixed JENKINS-60822 . It sound to be a very similar issue. Think you can take a look at this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204182.1579617297000.7422.1580226420202%40Atlassian.JIRA.
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title
Pascal Laporte updated an issue
Jenkins / JENKINS-60831
Localisation to non-english is causing a lot of issues, bug and crashes
Change By:
Pascal Laporte
We were running version 2.182 of Jenkins.Since we have update to version 2.214 there is a lot of issue if we aren't running out browser in other language than english.For example, it is impossible to add parameters to a job. 1. The button itself isn't decorated properly. And pressing it won't do anything.2. Running a job without parameters (already created job). Will cause a Jenkins Crash: {code:java}net.sf.json.JSONException: A JSONObject text must begin with '{' at character 1 of init{code}And if we look at the request post. There is indeed a second json within the header !Body.png|width=438,height=114,thumbnail! Other language than french seem to be affected. We have tried with spanish and get the same result. Also, within the console we are seeing a this error:!page-init.png! Thanks for your help!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title
Pascal Laporte updated an issue
Jenkins / JENKINS-60831
Localisation to non-english is causing a lot of issues, bug and crashes
Change By:
Pascal Laporte
We were running version 2.182 of Jenkins.Since we have update to version 2.214 there is a lot of issue if we aren't running out browser in other language than english.For example, it is impossible to add parameters to a job. 1. The button itself isn't decorated properly. And pressing it won't do anything.2. Running a job without parameters (already created job). Will cause a Jenkins Crash: {code:java}net.sf.json.JSONException: A JSONObject text must begin with '{' at character 1 of init{code}And if we look at the request post. There is indeed a second json within the header !image-2020-01-21-09-30-54-656.png! Other language than french seem to be affected. We have tried with spanish and get the same result. Also, within the console we are seeing a this error:!page-init.png! Thanks for your help!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Pascal Laporte updated an issue Jenkins / JENKINS-60831 Localisation to non-english is causing a lot of issues, bug and crashes Change By: Pascal Laporte Attachment: Body.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204182.1579617297000.3205.1579617960402%40Atlassian.JIRA.
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Pascal Laporte updated an issue Jenkins / JENKINS-60831 Localisation to non-english is causing a lot of issues, bug and crashes Change By: Pascal Laporte Attachment: Body.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204182.1579617297000.3206.1579617960494%40Atlassian.JIRA.
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title
Pascal Laporte created an issue
Jenkins / JENKINS-60831
Localisation to non-english is causing a lot of issues, bug and crashes
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Body.png, page-init.png
Components:
core
Created:
2020-01-21 14:34
Environment:
Jenkins: 2.214, chrome and firefox
Priority:
Critical
Reporter:
Pascal Laporte
We were running version 2.182 of Jenkins. Since we have update to version 2.214 there is a lot of issue if we aren't running out browser in other language than english. For example, it is impossible to add parameters to a job. 1. The button itself isn't decorated properly. And pressing it won't do anything. 2. Running a job without parameters (already created job). Will cause a Jenkins Crash:
net.sf.json.JSONException: A JSONObject text must begin with '{' at character 1 of init
And if we look at the request post. There is indeed a second json within the header Other language than french seem to be affected. We have tried with spanish and get the same result. Also, within the console we are seeing a this error: Thanks for your help!
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Pascal Laporte commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed Antonio Muñiz Could you please release the plugins version that include this fix? The last version, 1.3.1 is 2 years old. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before Carlos SanchezYou are a hero. With 4096 we are starting to see the magic operate (2~3 sec)! Thanks a lot! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before Carlos Sanchez I'm very sad to report that it is still slow Using the first provided example, we get a good 6~7 sec (with kubernetes-plugins (unreleased) 1.14.7 ). It is better than the 9~10 sec from previous versions, but still slow. And we have 2~3 sec without the env variables injection. I will probably open a new issue since versions of jenkins, kubernetes, and plugins have changed... 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55688) Anchore Whitelisted Images not shown in report
Title: Message Title Pascal Laporte created an issue Jenkins / JENKINS-55688 Anchore Whitelisted Images not shown in report Issue Type: Improvement Assignee: Daniel Nurmi Components: anchore-container-scanner-plugin Created: 2019-01-18 18:09 Environment: anchore-container-scanner-plugin: 1.0.18 jenkins-core: 2.147 Priority: Minor Reporter: Pascal Laporte The Jenkins plugins is super awesome! But… in the case of whitelisted_images, I feel sad that it doesn’t show within the report that it pass because it was whitelisted. For example: 1- Seending multiples images to scan/evaluate. 2- Jenkins mark the job has failed, because some images aren’t compilant with the policies (Great!) 3- Looking at the report we see that every image are having problem. So people, aren’t able to see which images should be fix and which are just to be ignored (because they were whitelisted). So people are trying to fix trouble that they shouldn't care about. Add Comment
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before We have already try to send a single WatchExec that combine all the env variable. It didn't changed much the resulting elapse on the total job. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte edited a comment on JENKINS-50429 Re: Shell command are really slower than before The only references that we have found during our timeboxed investigation was:[https://github.com/fabric8io/kubernetes-client/issues/1008] Since we don't use Jenkins variable injection in pods. We are using the «env.VARIABLE» style. We have ended up with commenting [https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/ContainerExecDecorator.java#L342-L364] Still Not the finest fix, but it solve our problem for the moment. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before The only references that we have found during our timeboxed investigation was: https://github.com/fabric8io/kubernetes-client/issues/1008 Since we don't use Jenkins variable injection in pods. We are using the «env.VARIABLE» style. We have ended up with commenting https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/ContainerExecDecorator.java#L342-L364 Still 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before We have done some investiation, it seem indeed that the environment variable injection to shell is the culprit here. However, the problem seem deeper than that and involve the fabric8 kubernetes Watchexec PipeInput which is really slow. Still, If the watch channel could be kept open during every step within a container steps and send the envVars only a single time could probably improve performance quite a lot. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before Carlos Sanchez Do you have any progress on this issue. We would like to upgrade our Kubernetes plugin. But, we won't be able until the performance issue with the «container» step is fix. Thanks for your help 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before This is only a generic test easy to reproduce. In our real pipeline we use multiple pod/node and containers. Checkout is generally done in the jnlp container, and all the other stuff is done within the others containers. Still, if we want to execute steps within a container (other than jnlp) we will have to invoque the container steps. 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte edited a comment on JENKINS-50429 Re: Shell command are really slower than before Version 1.2.1 is probably the worst: we are getting a 18 seconds score.We are running every test within containers. (Running on master or ssh slaves is super fast, >1sec) I have added a visual of the stage timing 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte updated an issue Jenkins / JENKINS-50429 Shell command are really slower than before Change By: Pascal Laporte Attachment: Screen.png 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before Version 1.2.1 is probably the worst: we are getting a 18 seconds score. We are running every test within containers. (Running on master or ssh slaves is super fast, >1sec) 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before I have retry with latest version of Jenkins 1.124 and latest version of Kubernetes plugin 1.6.3 on a local setup I'm getting 10 seconds for the sample job. Taking the same installation and if I install kubernetes plugin 1.2, I am getting a 2 seconds result. Carlos Sanchez Do you have any idea? I don't like the idea of being stuck at a specific version for a specific plugin. 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte updated an issue Jenkins / JENKINS-50429 Shell command are really slower than before Change By: Pascal Laporte Environment: jenkins 2.111,workflow-durable-task-step 2.19 kubernetes-1.6.0 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before I have setup a new local Kubernetes and have pin point the problem to the Kubernetes Plugin. We have been able to point to the exact version of the plugins that is introducing the slowness. Everything is working within the 3 second (acceptable time) with version 1.2 of kubernetes plugin and with version 1.2.1 and up we get the ultra slow steps. 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte edited a comment on JENKINS-50429 Re: Shell command are really slower than before [~svanoort] Couple of answer for you: # Using a traditional agents (ssh) is getting a 1 second run time. So yes it seem to happen only on containers. # For this precise exemple we don't see higher or alaerming alarming CPU usage on the master node. # Attach to the issus is now a threadDump of the master node.Extra info, the master node is also a Kubernetes Pods (container), running the same job on the master is taking 1 second. 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte updated an issue Jenkins / JENKINS-50429 Shell command are really slower than before Change By: Pascal Laporte Attachment: masterThread_Dump.log 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before Sam Van Oort Couple of answer for you: Using a traditional agents (ssh) is getting a 1 second run time. So yes it seem to happen only on containers. For this precise exemple we don't see higher or alaerming CPU usage on the master node. Attach to the issus is now a threadDump of the master node. Extra info, the master node is also a Kubernetes Pods (container), running the same job on the master is taking 1 second. 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-50429) Shell command are really slower than before
Title: Message Title
Pascal Laporte commented on JENKINS-50429
Re: Shell command are really slower than before
We don't have try to pin point the exact version of which component is causing us trouble. We don't have the feeling that cheetsh is really involve with the slowness. We have tried an older version of Jenkins core (2.101 and 2.93) but it was impossible for use to have the exact same plugins versions that we had before. To be fair, we were out dated on 2 plugins since 2.93. The kubernetes-plugin and the durable-task. We run most of the jobs in a kubernetes pod Here is a reference build run:
node("slavenode"){ // <-- This is a K8s pod
stage('checkout'){
container("jnlp"){
deleteDir()
sh "touch A"
sh "chmod a+x A"
sh "ls -la"
stash name: 'artefact', includes: "A"
deleteDir()
unstash 'artefact'
sh "ls -la"
}
}
}
The stage was reported to run in 4~5 second (so it doesn't include spawning a new pod). With the new version we get a good 13~15 seconds.
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,
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte created an issue Jenkins / JENKINS-50429 Shell command are really slower than before Issue Type: Bug Assignee: Unassigned Components: workflow-durable-task-step-plugin Created: 2018-03-27 12:34 Environment: jenkins 2.111, workflow-durable-task-step 2.19 Priority: Minor Reporter: Pascal Laporte We have recently updated our Jenkins installation from 2.101 to 2.111 including every plugin related to pipeline. Since this update every shell «sh» invocation is really slower than before. shell invocation was taking few millisecond before. it is now taking seconds. So job that were taking 1:30 minutes or taking up to 25:00 minutes. We are trying to figure out which plugin is related Add Comment
[JIRA] (JENKINS-42316) Log report corrupted content in durable-*/pid
Title: Message Title
Pascal Laporte created an issue
Jenkins / JENKINS-42316
Log report corrupted content in durable-*/pid
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
durable-task-plugin, kubernetes-plugin
Created:
2017/Feb/24 11:06 PM
Environment:
jenkins 2.47 kubernetes-plugin 0.11 durable-task-plugin 1.13
Labels:
kubernetes pipeline container
Priority:
Minor
Reporter:
Pascal Laporte
Within a container, generated with kubernetes (using kubernetes-plugin), a simple process invocation will generate multiple time this log:
...
Cannot contact kubernetes-c4df03a7122e48a5a094643522eca149-2f29e02b2bb2: java.io.IOException: corrupted content in /home/jenkins/workspace/POPOPOPO@tmp/durable-a2a574cd/pid: java.lang.NumberFormatException: For input string: ""
...
Here is a simple pipeline to easily reproduce:
podTemplate(label: 'mypod', containers: [])
{
stage("Test"){
node("mypod"){
container("jnlp"){
sh '''
echo "#!/bin/sh
sleep 10" > popo.sh
chmod a+x popo.sh
./popo.sh
'''
}
}
}
}
[JIRA] (JENKINS-42315) PodTemplate is now mandatory within pipeline
Title: Message Title
Pascal Laporte created an issue
Jenkins / JENKINS-42315
PodTemplate is now mandatory within pipeline
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2017/Feb/24 10:46 PM
Environment:
jenkins 2.47 kubernetes-plugin 0.11
Labels:
pipeline kubernetes
Priority:
Major
Reporter:
Pascal Laporte
Before version 0.11 We were able to declare in the global jenkins configuration a PodTemplate with containers. Here an simple pipeline example that was working with a global PodTemplate with 0.10
stage("Example"){
node("mypod"){
container("golang"){
sh '''
echo "something"
'''
}
}
}
With 0.11 we get an error:
org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class org.csanchez.jenkins.plugins.kubernetes.pipeline.PodTemplateStep is missing
It is now (with 0.11) mandatory to have the PodTemplate and containers declare within the
[JIRA] (JENKINS-40699) Post-stage/build test results etc doesn't play well with parallel on multiple nodes
Title: Message Title Pascal Laporte commented on JENKINS-40699 Re: Post-stage/build test results etc doesn't play well with parallel on multiple nodes We do have the same problem. Would have thought that the «post» declarative would be able to be set for each parallel task. But it is only available in the top-level pipeline block and in each stage block. Back to the «try/catch/finally» hack. 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.
