[JIRA] (JENKINS-61584) Method java.util.regex.Matcher find is no longer whitelisted
Title: Message Title Reinhold Füreder commented on JENKINS-61584 Re: Method java.util.regex.Matcher find is no longer whitelisted Thanks Devin Nusbaum! (Also thanks for taking a closer look and re-adding three more accidentally lost signatures...) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205281.158462305.14442.1587449760189%40Atlassian.JIRA.
[JIRA] (JENKINS-61584) Method java.util.regex.Matcher find is no longer whitelisted
Title: Message Title Reinhold Füreder edited a comment on JENKINS-61584 Re: Method java.util.regex.Matcher find is no longer whitelisted Many duplicate issues (25x): JENKINS-61553 ... JENKINS-61584, just search for "_Method java.util.regex.Matcher find is no longer whitelisted_" and component "_script-security-plugin_" => I don't have sufficient permissions for JIRA bulk change...And because this is a rather log hanging fruit I dare to assign this one to [~bitwiseman] (as he merged the culprit JENKINS-59952), although maybe [~haridsv] might be appropriate as well? [~wolniewicz] I think your finger was a bit nervous when filing the issues? Sorry, couldn't resist ;-) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205281.158462305.12295.1587024300197%40Atlassian.JIRA.
[JIRA] (JENKINS-61584) Method java.util.regex.Matcher find is no longer whitelisted
Title: Message Title Reinhold Füreder assigned an issue to Liam Newman Jenkins / JENKINS-61584 Method java.util.regex.Matcher find is no longer whitelisted Change By: Reinhold Füreder Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205281.158462305.12290.1587024180392%40Atlassian.JIRA.
[JIRA] (JENKINS-61584) Method java.util.regex.Matcher find is no longer whitelisted
Title: Message Title Reinhold Füreder commented on JENKINS-61584 Re: Method java.util.regex.Matcher find is no longer whitelisted Many duplicate issues (25x): JENKINS-61553 ... JENKINS-61584, just search for "Method java.util.regex.Matcher find is no longer whitelisted" and component "script-security-plugin" => I don't have sufficient permissions for JIRA bulk change... And because this is a rather log hanging fruit I dare to assign this one to Liam Newman (as he merged the culprit JENKINS-59952), although maybe Hari Dara might be appropriate as well? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205281.158462305.12287.1587024180291%40Atlassian.JIRA.
[JIRA] (JENKINS-61927) Add category to system settings for modern Jenkins releases
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-61927
Add category to system settings for modern Jenkins releases
Change By:
Reinhold Füreder
I think this plugin should show up in category "Security" in "Manage Jenkins" page of modern Jenkins releases (currently it is "Uncategorized"):* implementation in analogy to e.g. https://github.com/jenkinsci/credentials-plugin/compare/credentials-2.3.3...credentials-2.3.4 or https://github.com/jenkinsci/configuration-as-code-plugin/pull/1358* see https://github.com/jenkinsci/jenkins/pull/4546 for more background* try to use {{ManagementLink.Category.SECURITY}}? Should be a rather low-hanging fruit...
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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
[JIRA] (JENKINS-61927) Add category to system settings for modern Jenkins releases
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-61927 Add category to system settings for modern Jenkins releases Issue Type: Improvement Assignee: Unassigned Components: script-security-plugin Created: 2020-04-16 07:38 Environment: Jenkins core >= 2.226 (2020-03-15), see https://github.com/jenkinsci/jenkins/pull/4546 for more details Priority: Minor Reporter: Reinhold Füreder I think this plugin should show up in category "Security" in "Manage Jenkins" page of modern Jenkins releases (currently it is "Uncategorized"): implementation in analogy to e.g. https://github.com/jenkinsci/credentials-plugin/compare/credentials-2.3.3...credentials-2.3.4 or https://github.com/jenkinsci/configuration-as-code-plugin/pull/1358 see https://github.com/jenkinsci/jenkins/pull/4546 for more background try to use ManagementLink.Category.SECURITY?
[JIRA] (JENKINS-61926) Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-61926
Re: Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull
Hm, I am seeing only one with respect to JCasC:{noformat}2020-04-16 06:49:32.148+ [id=34]WARNING jenkins.model.Jenkins$5#runTask: ConfigurationAsCode.init failed perhaps due to plugin dependency issuesjava.lang.ClassNotFoundException: javax.annotation.Nonnullat jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1387)at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342)at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1089)at java.lang.ClassLoader.loadClass(ClassLoader.java:352)Caused: java.lang.NoClassDefFoundError: javax/annotation/Nonnullat io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:118)at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:77)at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:267)at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:101)at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:344)at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:287)at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:352)at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:287)at io.jenkins.plugins.casc.ConfigurationAsCode.lambda$checkWith$7(ConfigurationAsCode.java:743)at io.jenkins.plugins.casc.ConfigurationAsCode.invokeWith(ConfigurationAsCode.java:693)at io.jenkins.plugins.casc.ConfigurationAsCode.checkWith(ConfigurationAsCode.java:743)at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:728)at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:608)at io.jenkins.plugins.casc.ConfigurationAsCode.configure(ConfigurationAsCode.java:291)at io.jenkins.plugins.casc.ConfigurationAsCode.init(ConfigurationAsCode.java:283)Caused: java.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)Caused: java.lang.Errorat hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110)at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1132)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748){noformat}And there is a corresponding release of JCasC available (see https://github.com/jenkinsci/configuration-as-code-plugin/releases/tag/configuration-as-code-1.39):{noformat}2020-04-16 06:49:36.682+ [id=41]INFO
[JIRA] (JENKINS-61926) Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull
Title: Message Title Reinhold Füreder commented on JENKINS-61926 Re: Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull Hm, I am seeing only one with respect to JCasC: 2020-04-16 06:49:32.148+ [id=34]WARNING jenkins.model.Jenkins$5#runTask: ConfigurationAsCode.init failed perhaps due to plugin dependency issues java.lang.ClassNotFoundException: javax.annotation.Nonnull at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1387) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1089) at java.lang.ClassLoader.loadClass(ClassLoader.java:352) Caused: java.lang.NoClassDefFoundError: javax/annotation/Nonnull at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:118) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:77) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:267) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:101) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:344) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:287) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:352) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:287) at io.jenkins.plugins.casc.ConfigurationAsCode.lambda$checkWith$7(ConfigurationAsCode.java:743) at io.jenkins.plugins.casc.ConfigurationAsCode.invokeWith(ConfigurationAsCode.java:693) at io.jenkins.plugins.casc.ConfigurationAsCode.checkWith(ConfigurationAsCode.java:743) at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:728) at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:608) at io.jenkins.plugins.casc.ConfigurationAsCode.configure(ConfigurationAsCode.java:291) at io.jenkins.plugins.casc.ConfigurationAsCode.init(ConfigurationAsCode.java:283) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) Caused: java.lang.Error at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1132) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-61890) JCasC warning log for GlobalJobDslSecurityConfiguration#metaClass
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-61890 JCasC warning log for GlobalJobDslSecurityConfiguration#metaClass Change By: Reinhold Füreder Summary: JCasC warning log for GlobalJobDslSecurityConfiguration #metaClass Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205762.1586850993000.10048.1586851380191%40Atlassian.JIRA.
[JIRA] (JENKINS-61890) JCasC warning log for GlobalJobDslSecurityConfiguration
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-61890 JCasC warning log for GlobalJobDslSecurityConfiguration Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2020-04-14 07:56 Labels: jcasc-compatibility Priority: Minor Reporter: Reinhold Füreder During Jenkins startup I get: WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class javaposse.jobdsl.plugin.GlobalJobDslSecurityConfiguration#metaClass: type is abstract but not Describable. => Extracted/moved the problem from (very generic issue) https://github.com/jenkinsci/configuration-as-code-plugin/issues/536 It seems that after updating JCasC plugin from 1.31 to 1.32 a similar warning appears during Jenkins startup that was not there before: 2019-10-10 14:56:50.519+ [id=119] WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class javaposse.jobdsl.plugin.GlobalJobDslSecurityConfiguration#metaClass: type is abstract but not Describable.
[JIRA] (JENKINS-54782) Support for Configuration as Code plugin
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-54782
Re: Support for Configuration as Code plugin
Jenkins startup log warnings from JCasC:{noformat}WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable.{noformat} * => Extracted/moved the problem from (very generic issue) [https://github.com/jenkinsci/configuration-as-code-plugin/issues/536] * {quote}After adding some more JCasC configurations (in comparison to before/above), I am now getting (only) the following warning during Jenkins startup (twice):{noformat}WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable.{noformat}I am pretty sure the JCasC context is the configuration of a "global library": this is the interesting parts of the "jenkins.yaml" file:{noformat}jenkins: ... securityRealm:ldap: ...credentials: system:domainCredentials:- credentials: ... - usernamePassword: scope: GLOBAL id: jenkins-ldap username: *** password: *** description: "Jenkins LDAP user and password credentials" ...unclassified: ... globalLibraries:libraries:- name: "acme-shared-library" defaultVersion: "trunk" allowVersionOverride: true includeInChangesets: false retriever:modernSCM: scm:subversion: remoteBase: "https:///" credentialsId: jenkins-ldap ...{noformat}These are all Jenkins logs relevant for this warning or the "global library" configuration (please mind but ignore the duplicate logging or are these maybe even temporary duplicate configuration object instantiations: this is another issue => #899):{noformat}...2019-06-11 10:06:43.572+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.LibraryConfiguration.name = acme-shared-library2019-06-11 10:06:43.576+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class jenkins.scm.impl.subversion.SubversionSCMSource.remoteBase = https:///2019-06-11 10:06:43.577+ [id=35]WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable.2019-06-11 10:06:43.578+ [id=35]INFOi.jenkins.plugins.casc.Attribute#setValue: Setting jenkins.scm.impl.subversion.SubversionSCMSource{id='4b43e974-7f07-4a35-9646-da9361bd0127'}.credentialsId = jenkins-ldap2019-06-11 10:06:43.578+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.scm = {subversion={}}2019-06-11 10:06:43.579+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.LibraryConfiguration.retriever = {modernSCM={}}2019-06-11 10:06:43.579+ [id=35]INFOi.jenkins.plugins.casc.Attribute#setValue: Setting org.jenkinsci.plugins.workflow.libs.LibraryConfiguration@40045ff7.allowVersionOverride = true2019-06-11 10:06:43.580+ [id=35]INFOi.jenkins.plugins.casc.Attribute#setValue: Setting org.jenkinsci.plugins.workflow.libs.LibraryConfiguration@40045ff7.defaultVersion = trunk2019-06-11 10:06:43.580+ [id=35]INFOi.jenkins.plugins.casc.Attribute#setValue: Setting org.jenkinsci.plugins.workflow.libs.LibraryConfiguration@40045ff7.includeInChangesets = false...2019-06-11 10:06:45.472+ [id=35]INFO
[JIRA] (JENKINS-54782) Support for Configuration as Code plugin
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-54782
Re: Support for Configuration as Code plugin
Jenkins startup log warnings from JCasC:{ { noformat} WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. {noformat } } => Extracted/moved the problem from (very generic issue) [https://github.com/jenkinsci/configuration-as-code-plugin/issues/536]{quote} After adding some more JCasC configurations (in comparison to before/above), I am now getting (only) the following warning during Jenkins startup (twice): { { noformat} WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. {noformat } } I am pretty sure the JCasC context is the configuration of a "global library": this is the interesting parts of the "jenkins.yaml" file: { { noformat} jenkins: }} {{ ... }} {{ securityRealm: }} {{ ldap: }} {{ ... }} {{ credentials: }} {{ system: }} {{ domainCredentials: }} - {{ credentials: }} {{ ... }} - {{ usernamePassword: }} {{ scope: GLOBAL }} {{ id: jenkins-ldap }} {{ username: *** }} {{ password: *** }} {{ description: "Jenkins LDAP user and password credentials" }} {{ ... }} {{ unclassified: }} {{ ... }} {{ globalLibraries: }} {{ libraries: }} - {{ name: "acme-shared-library" }} {{ defaultVersion: "trunk" }} {{ allowVersionOverride: true }} {{ includeInChangesets: false }} {{ retriever: }} {{ modernSCM: }} {{ scm: }} {{ subversion: }} {{ remoteBase: "https:///" }} {{ credentialsId: jenkins-ldap }} {{ ... {noformat } } These are all Jenkins logs relevant for this warning or the "global library" configuration (please mind but ignore the duplicate logging or are these maybe even temporary duplicate configuration object instantiations: this is another issue => #899): { { noformat} ... }} {{ 2019-06-11 10:06:43.572+ [id=35] INFO i.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.LibraryConfiguration.name = acme-shared-library }} {{ 2019-06-11 10:06:43.576+ [id=35] INFO i.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class jenkins.scm.impl.subversion.SubversionSCMSource.remoteBase = https:/// }} {{ 2019-06-11 10:06:43.577+ [id=35] WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. }} {{ 2019-06-11 10:06:43.578+ [id=35] INFO i.jenkins.plugins.casc.Attribute#setValue: Setting jenkins.scm.impl.subversion.SubversionSCMSource }} { {Unknown macro: \{ id='4b43e974-7f07-4a35-9646-da9361bd0127'} }}{{ .credentialsId = jenkins-ldap }} {{ 2019-06-11 10:06:43.578+ [id=35] INFO i.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.scm = \ {subversion={}} }} {{ 2019-06-11 10:06:43.579+ [id=35] INFO i.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.LibraryConfiguration.retriever = \ {modernSCM={}} }} {{ 2019-06-11 10:06:43.579+ [id=35] INFO i.jenkins.plugins.casc.Attribute#setValue: Setting org.jenkinsci.plugins.workflow.libs.LibraryConfiguration@40045ff7.allowVersionOverride = true }} {{ 2019-06-11 10:06:43.580+ [id=35] INFO i.jenkins.plugins.casc.Attribute#setValue: Setting org.jenkinsci.plugins.workflow.libs.LibraryConfiguration@40045ff7.defaultVersion = trunk }} {{ 2019-06-11 10:06:43.580+ [id=35] INFO
[JIRA] (JENKINS-54782) Support for Configuration as Code plugin
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-54782
Re: Support for Configuration as Code plugin
Jenkins startup log warnings from JCasC: ``` {{ WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. }} ``` => Extracted/moved the problem from (very generic issue) [ https://github.com/jenkinsci/configuration-as-code-plugin/issues/536 ] {quote} After adding some more JCasC configurations (in comparison to before/above), I am now getting (only) the following warning during Jenkins startup (twice): ``` {{ WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. }} ``` I am pretty sure the JCasC context is the configuration of a "global library": this is the interesting parts of the "jenkins.yaml" file: ``` {{ jenkins: }} {{ ... }} {{ securityRealm: }} {{ ldap: }} {{ ... }} {{ credentials: }} {{ system: }} {{ domainCredentials: }} - {{ credentials: }} {{ ... }} - {{ usernamePassword: }} {{ scope: GLOBAL }} {{ id: jenkins-ldap }} {{ username: *** }} {{ password: *** }} {{ description: "Jenkins LDAP user and password credentials" }} {{ ... }} {{ unclassified: }} {{ ... }} {{ globalLibraries: }} {{ libraries: }} - {{ name: "acme-shared-library" }} {{ defaultVersion: "trunk" }} {{ allowVersionOverride: true }} {{ includeInChangesets: false }} {{ retriever: }} {{ modernSCM: }} {{ scm: }} {{ subversion: }} {{ remoteBase: "https:///" }} {{ credentialsId: jenkins-ldap }} {{ ... }} ``` These are all Jenkins logs relevant for this warning or the "global library" configuration (please mind but ignore the duplicate logging or are these maybe even temporary duplicate configuration object instantiations: this is another issue => #899): ``` {{ ... }} {{ 2019-06-11 10:06:43.572+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.LibraryConfiguration.name = acme-shared-library }} {{ 2019-06-11 10:06:43.576+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class jenkins.scm.impl.subversion.SubversionSCMSource.remoteBase = https:/// }} {{ 2019-06-11 10:06:43.577+ [id=35]WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. }} {{ 2019-06-11 10:06:43.578+ [id=35]INFOi.jenkins.plugins.casc.Attribute#setValue: Setting jenkins.scm.impl.subversion.SubversionSCMSource }} { {Unknown macro: \{ id='4b43e974-7f07-4a35-9646-da9361bd0127'} }}{{ .credentialsId = jenkins-ldap }} {{ 2019-06-11 10:06:43.578+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.scm = \ {subversion={}} }} {{ 2019-06-11 10:06:43.579+ [id=35]INFOi.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.LibraryConfiguration.retriever = \ {modernSCM={}} }} {{ 2019-06-11 10:06:43.579+ [id=35]INFOi.jenkins.plugins.casc.Attribute#setValue: Setting org.jenkinsci.plugins.workflow.libs.LibraryConfiguration@40045ff7.allowVersionOverride = true }} {{ 2019-06-11 10:06:43.580+ [id=35]INFO
[JIRA] (JENKINS-54782) Support for Configuration as Code plugin
Title: Message Title
Reinhold Füreder commented on JENKINS-54782
Re: Support for Configuration as Code plugin
Jenkins startup log warnings from JCasC: ``` WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. ``` => Extracted/moved the problem from (very generic issue) https://github.com/jenkinsci/configuration-as-code-plugin/issues/536
After adding some more JCasC configurations (in comparison to before/above), I am now getting (only) the following warning during Jenkins startup (twice): ``` WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. ```
I am pretty sure the JCasC context is the configuration of a "global library": this is the interesting parts of the "jenkins.yaml" file: ``` jenkins: ...
securityRealm: ldap: ...
credentials: system: domainCredentials:
credentials: ...
usernamePassword: scope: GLOBAL id: jenkins-ldap username: *** password: *** description: "Jenkins LDAP user and password credentials" ...
unclassified: ... globalLibraries: libraries:
name: "acme-shared-library" defaultVersion: "trunk" allowVersionOverride: true includeInChangesets: false retriever: modernSCM: scm: subversion: remoteBase: "https:///" credentialsId: jenkins-ldap ... ```
These are all Jenkins logs relevant for this warning or the "global library" configuration (please mind but ignore the duplicate logging or are these maybe even temporary duplicate configuration object instantiations: this is another issue => #899): ``` ... 2019-06-11 10:06:43.572+ [id=35] INFO i.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class org.jenkinsci.plugins.workflow.libs.LibraryConfiguration.name = acme-shared-library 2019-06-11 10:06:43.576+ [id=35] INFO i.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class jenkins.scm.impl.subversion.SubversionSCMSource.remoteBase = https:/// 2019-06-11 10:06:43.577+ [id=35] WARNING i.j.p.casc.BaseConfigurator#createAttribute: Can't handle class jenkins.scm.impl.subversion.SubversionSCMSource#owner: type is abstract but not Describable. 2019-06-11 10:06:43.578+ [id=35] INFO i.jenkins.plugins.casc.Attribute#setValue: Setting jenkins.scm.impl.subversion.SubversionSCMSource
Unknown macro: {id='4b43e974-7f07-4a35-9646-da9361bd0127'}
.credentialsId = jenkins-ldap 2019-06-11 10:06:43.578+ [id=35] INFO i.j.p.c.i.c.DataBoundConfigurator#tryConstructor: Setting class
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder resolved as Duplicate Daniel Beck I therefore dared to close this issue as duplicate of JENKINS-61687 (and making you the assignee of this issue, as you stated/confirmed that it is a duplicate) Jenkins / JENKINS-61256 Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Change By: Reinhold Füreder Status: Open Resolved Assignee: Daniel Beck Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder commented on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder I think the "just deleting in UI does not help" was in the meantime fixed by JENKINS-61688 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.4089.1585739460134%40Atlassian.JIRA.
[JIRA] (JENKINS-61757) Global Variable Reference HTML documentation strips tags
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-61757
Global Variable Reference HTML documentation strips tags
Change By:
Reinhold Füreder
After quite some time I accidentally checked the "Pipeline Syntax > Global Variable Reference" for my shared Jenkins pipeline library and saw that the "" tags are now (unfortunately I can't remember when it was still OK, I just know that it used to be OK for a long time) stripped. Since it is about documentation of usage of shared pipeline library I claim that multi-line coding examples in such ""tags is fairly common...Example: For a file called "acme.txt" with the following content { { noformat} ...Example:acme.build {node { ...} } ... {noformat } } ..., the resulting HTML will looks like: { { noformat} ...Example:acme.build {node { ...} }... {noformat } } And using an additional "" inside the "" section, does not help either. But at least is kept...
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61757) Global Variable Reference HTML documentation strips tags
Title: Message Title
Reinhold Füreder created an issue
Jenkins / JENKINS-61757
Global Variable Reference HTML documentation strips tags
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-03-31 12:54
Priority:
Major
Reporter:
Reinhold Füreder
After quite some time I accidentally checked the "Pipeline Syntax > Global Variable Reference" for my shared Jenkins pipeline library and saw that the "" tags are now (unfortunately I can't remember when it was still OK, I just know that it used to be OK for a long time) stripped. Since it is about documentation of usage of shared pipeline library I claim that multi-line coding examples in such ""tags is fairly common... Example: For a file called "acme.txt" with the following content {{... Example: acme.build { node { ... } } ...}} ..., the resulting HTML will looks like: {{ ... Example: acme.build { node { ... } } ... }} And using an additional "" inside the "" section, does not help either. But at least is kept...
Add Comment
[JIRA] (JENKINS-54783) Library additions to Global Variable Reference are not displayed formatted
Title: Message Title Reinhold Füreder commented on JENKINS-54783 Re: Library additions to Global Variable Reference are not displayed formatted In https://jenkins.io/doc/book/pipeline/shared-libraries/ "Directory structure": The matching .txt, if present, can contain documentation, processed through the system’s configured markup formatter (so may really be HTML, Markdown, etc., though the .txt extension is required). This documentation will only be visible on the Global Variable Reference pages that are accessed from the navigation sidebar of Pipeline jobs that import the shared library. In addition, those jobs must run successfully once before the shared library documentation will be generated. => So it is not too bad anymore? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.195591.1542918809000.3575.1585658580219%40Atlassian.JIRA.
[JIRA] (JENKINS-61412) UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder
Title: Message Title Reinhold Füreder commented on JENKINS-61412 Re: UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder Veaceslav Gaidarji thanks for the extremely quick fix Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205069.1583843413000.6195.1584009780100%40Atlassian.JIRA.
[JIRA] (JENKINS-61412) UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-61412 UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder Issue Type: Bug Assignee: Veaceslav Gaidarji Components: plot-plugin Created: 2020-03-10 12:30 Environment: Jenkins Core 2.223 Jenkins Plot Plugin 2.1.5 Priority: Critical Reporter: Reinhold Füreder After upgrade from Jenkins Plot Plugin 2.1.4 => 2.1.5 Jenkins log: 2020-03-10 10:40:02.722+ [id=177] WARNING o.j.p.s.d.DescribableParameter#uncoerce: failed to uncoerce hudson.plugins.plot.PlotBuilder@4bf77f69 java.lang.UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder at org.jenkinsci.plugins.structs.describable.DescribableParameter.getValue(DescribableParameter.java:161) at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:655) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2_(DescribableModel.java:752) at org.jenkinsci.plugins.structs.describable.DescribableParameter.uncoerce(DescribableParameter.java:196) at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:655) at
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder commented on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Note that just deleting it in UI does not help in case JCasC is used: after a restart it (the new global default project/job build discarder) re-appears... ... unclassified: buildDiscarders: configuredBuildDiscarders: - "jobBuildDiscarder" => Workaround/Fix: Adapting JCasC YAML configuration file ... unclassified: buildDiscarders: configuredBuildDiscarders: [] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.732.1582807680125%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-61256
Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
[~danielbeck] This issue is certainly related to Jenkins core v2.221 ( [ https://github.com/jenkinsci/jenkins/pull/4368 ] ):{quote}Jenkins will by default execute the configured per-project build discarder periodically even if no build is currently finishing. This may delete old builds of projects that got a more aggressive build discarder configuration since the last build was run. (pull 4368) {quote}Not sure if it could be also related to JENKINS-60716, but I hope/think it should be fixed by preventing this race condition?I also think this is a different problem than in JENKINS-52230.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204823.1582799473000.677.1582800360069%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-61256
Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
[~danielbeck] This issue is certainly related to Jenkins core v2.221 (https://github.com/jenkinsci/jenkins/pull/4368):{quote}Jenkins will by default execute the configured per-project build discarder periodically even if no build is currently finishing. This may delete old builds of projects that got a more aggressive build discarder configuration since the last build was run. (pull 4368) {quote} Not sure if it could be also related to JENKINS-60716, but I hope/think it should be fixed by preventing this race condition?I also think this is a different problem than in JENKINS-52230. Presumably related/caused by https://github.com/jenkinsci/jenkins/pull/4368
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204823.1582799473000.676.158280075%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder edited a comment on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Not sure if it could be also related to JENKINS-60716, but I hope/think it should be fixed by preventing this race condition?I also think this is a different problem than in JENKINS-52230. Presumably related/caused by https://github.com/jenkinsci/jenkins/pull/4368 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.675.1582799820269%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder edited a comment on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Not sure if it could be also related to JENKINS-60716, but I hope/think it should be fixed by preventing this race condition? I also think this is a different problem than in JENKINS-52230. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.672.1582799640055%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder commented on JENKINS-61256 Re: Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Not sure if it could be also related to JENKINS-60716, but I hope/think it should be fixed by preventing this race condition? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204823.1582799473000.671.1582799580057%40Atlassian.JIRA.
[JIRA] (JENKINS-61256) Warning log spam due to new (default) BackgroundGlobalBuildDiscarder
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-61256 Warning log spam due to new (default) BackgroundGlobalBuildDiscarder Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-02-27 10:31 Environment: After updating Jenkins core 2.220 => 2.222 Priority: Major Reporter: Reinhold Füreder After updating Jenkins core 2.220 => 2.222 this morning I often see such warning logs, but not necessarily every time a build ends (I think). I naively guess this might be a kind of race condition between the project pipeline's build discarder and the new default BackgroundGlobalBuildDiscarder. Example with "ACME-Pipeline": Builds: Build #328: 20200227-094910-revb07cd7f2 (27-Feb-2020 09:49) Started by manual triggering by Build #329: 20200227-100803-revb07cd7f2 (27-Feb-2020 10:08) Started by manual triggering by Build #330: 20200227-102515-revb8388d5e (27-Feb-2020 10:25) Started by GitLab push by (Mind Jenkins log timestamps in UTC format: 1h behind local time) Build #254 is deleted at ~09:15:57 (UTC), i.e. ~10:15:57 (local time), becase build #329 finished at that time: ... 2020-02-27 08:57:05.977+ [id=3886] INFOo.j.p.workflow.job.WorkflowRun#finish: ACME/ACME-Pipeline #328 completed: UNSTABLE 2020-02-27 08:57:06.029+ [id=52]WARNING
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
Reinhold Füreder commented on JENKINS-53649
Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
I would also be very happy about this issue being resolved (in order to nicely show a parameter value) and actually would have hoped that this is easy for someone like Liam Newman (of course I am not just trying to challenge him in any way )... The workaround with sh step using label attribute also requires a node wrapping context and thus is quite some runtime overhead too. JENKINS-55612 could also be considered some overhead with respect to written pipeline code. I am quite confused/concerned/surprised about the mentioned/found inconsistencies and whether or not this is actually on purpose (cf. parameter and env values) and why? Another workaround is adding a non-printable anywhere in the middle, e.g. for an URL parameter: echo "URL: '${params.URL.replace('.', '.\u007F')}'"
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.194144.1537309242000.6756.1581425042629%40Atlassian.JIRA.
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title Reinhold Füreder commented on JENKINS-60822 Re: can't parse argument number: changelog.url Jesse Glick I had a closer look now for verification – actually I think/claim it is the really same issue, but the stacktrace above was taken from the web UI (as a kind of symptom); and in the Jenkins server log I actually found the "right" one: 2020-01-21 06:23:06.464+ [id=98]WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkins.acme.com/view/ACME/job/ACME/job/ACME-Deployment-Pipeline/build org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.214.jar!/hudson/model/UpdateCenter/CoreUpdateMonitor/message.jelly:53:20: can't parse argument number: changelog.url at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title
Reinhold Füreder commented on JENKINS-60822
Re: can't parse argument number: changelog.url
A colleague (also using browser language German) seems to have stumbled over the same problem – with a quite different failure symptom – when triggering a parameterized build (see stacktrace below): => Forcing "English" also helped here
net.sf.json.JSONException: A JSONObject text must begin with '{' at character 1 of init
at net.sf.json.util.JSONTokener.syntaxError(JSONTokener.java:499)
at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:919)
at net.sf.json.JSONObject._fromString(JSONObject.java:1145)
at net.sf.json.JSONObject.fromObject(JSONObject.java:162)
at net.sf.json.JSONObject.fromObject(JSONObject.java:132)
at org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:1020)
at hudson.model.ParametersDefinitionProperty._doBuild(ParametersDefinitionProperty.java:143)
at jenkins.model.ParameterizedJobMixIn.doBuild(ParameterizedJobMixIn.java:211)
at jenkins.model.ParameterizedJobMixIn$ParameterizedJob.doBuild(ParameterizedJobMixIn.java:407)
at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:760)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)
at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Reinhold Füreder edited a comment on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Oh yes, Support Core Plugin was changed: https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66 or https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66#diff-79928e08589e1f90af352ccce49d8eb0L274-L275 https://github.com/jenkinsci/support-core-plugin/commit/4a3c12403766f8e28386df1d2bd9757e3ec2fae7 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.204135.1579238976000.866.1579239960129%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Reinhold Füreder commented on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Oh yes, Support Core Plugin was changed: https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66 or https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66#diff-79928e08589e1f90af352ccce49d8eb0L274-L275 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.204135.1579238976000.864.1579239900128%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-60805
NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Change By:
Reinhold Füreder
First seen yesterday (and only once so far) after upgrading plugins:* cloudbees-jenkins-advisor:3.0.1 (from 3.0)* support-core:2.66 (from 2.65)A bit before there were other but IMHO potentially rather non-related plugin updates:* ant:1.11* cloudbees-folder:6.11* antisamy-markup-formatter:1.8* credentials:2.3.1* workflow-support:3.4* mailer:1.30* ssh-credentials:1.18.1* Office-365-Connector:4.12.2{noformat}2020-01-16 15:12:36.908+ [id=19]WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: it.components in /cloudbees-jenkins-advisor/. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.NoSuchMethodError: com.cloudbees.jenkins.support.SupportPlugin.getComponents()Lhudson/ExtensionList;at com.cloudbees.jenkins.plugins.advisor.AdvisorGlobalConfiguration.getComponents(AdvisorGlobalConfiguration.java:286)Caused: java.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94)at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-60805 NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Issue Type: Bug Assignee: Emilio Escobar Components: cloudbees-jenkins-advisor-plugin, support-core-plugin Created: 2020-01-17 05:29 Environment: The latest and greatest ;-) E.g. Jenkins core 2.214 Priority: Minor Reporter: Reinhold Füreder First seen yesterday (and only once so far) after upgrading plugins: cloudbees-jenkins-advisor:3.0.1 (from 3.0) support-core:2.66 (from 2.65) A bit before there were other but IMHO potentially rather non-related plugin updates: ant:1.11 cloudbees-folder:6.11 antisamy-markup-formatter:1.8 credentials:2.3.1 workflow-support:3.4 mailer:1.30 ssh-credentials:1.18.1 Office-365-Connector:4.12.2
[JIRA] (JENKINS-60688) waitUntil step snippet generation failure
Title: Message Title
Reinhold Füreder created an issue
Jenkins / JENKINS-60688
waitUntil step snippet generation failure
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-basic-steps-plugin
Created:
2020-01-08 09:55
Priority:
Minor
Reporter:
Reinhold Füreder
For "waitUntil" step the "Pipeline Syntax: Snippet Generator > Generate Pipeline Script" generates the error message:
no public field ‘initialRecurrencePeriod’ (or getter method) found in class org.jenkinsci.plugins.workflow.steps.WaitForConditionStep
Jenkins log:
2020-01-07 15:45:54.094+ [id=9177] WARNING o.j.p.workflow.cps.Snippetizer#doGenerateSnippet: failed to render {"initialRecurrencePeriod": "300", "stapler-class": "org.jenkinsci.plugins.workflow.steps.WaitForConditionStep", "$class": "org.jenkinsci.plu
gins.workflow.steps.WaitForConditionStep"}
java.lang.UnsupportedOperationException: no public field ‘initialRecurrencePeriod’ (or getter method) found in class org.jenkinsci.plugins.workflow.steps.WaitForConditionStep
at org.jenkinsci.plugins.structs.describable.DescribableParameter.getValue(DescribableParameter.java:161)
at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142)
at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:655)
at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2_(DescribableModel.java:752)
at
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Reinhold Füreder commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Devin Nusbaum I can confirm that your fix works really fine! Because – now some coughing and red face – I accidentally restarted Jenkins master without waiting for pipelines to complete (of course looking forward to JENKINS-60434): and there were some non-minor real world pipelines running... Just one of them failed due to JENKINS-49365... 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.169794.1460663849000.11279.1576652943246%40Atlassian.JIRA.
[JIRA] (JENKINS-49365) Resuming of pipelines vs. docker.image(...).inside(...)?
Title: Message Title
Reinhold Füreder commented on JENKINS-49365
Re: Resuming of pipelines vs. docker.image(...).inside(...)?
This problem has definitely re-occurred, because I accidentally restarted Jenkins master without waiting for pipelines to complete (cf. JENKINS-60434):
...
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withDockerRegistry
[Pipeline] {
[Pipeline] isUnix
[Pipeline] sh
07:34:43 + docker inspect -f . acme/mytool:13
07:34:43
07:34:43 Error: No such object: acme/mytool:13
[Pipeline] isUnix
[Pipeline] sh
07:34:43 + docker inspect -f . dockerregistry.acme.com/acme/mytool:13
07:34:43 .
[Pipeline] withDockerContainer
07:34:43 Jenkins does not seem to be running inside a container
07:34:43 $ docker run -t -d -u 10112:10005 --network=none -w /var/lib/jenkins/workspace/MyProject/MyProject-Pipeline-WS -v /var/lib/jenkins/workspace/MyProject/MyProject-Pipeline-WS:/var/lib/jenkins/workspace/MyProject/MyProject-Pipeline-WS:rw,z -v /var/lib/jenkins/workspace/MyProject/MyProject-Pipeline-WS@tmp:/var/lib/jenkins/workspace/MyProject/MyProject-Pipeline-WS@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e dockerregistry.acme.com/acme/mytool:13 cat
07:34:44 $ docker top 0a46f91e3a89720908a64eef2c8ac3688115a6472cb34161abec37b6bfc68e67 -eo pid,comm
[Pipeline] {
[Pipeline] lock
07:34:44 Trying to acquire lock on [Label: MyTool, Quantity: 1]
07:34:44 Lock acquired on [Label: MyTool, Quantity: 1]
[Pipeline] {
[Pipeline] pwd
[Pipeline] sh
07:34:44 + ... /opt/mytool/bin/...sh /var/lib/jenkins/workspace/MyProject/MyProject-Pipeline-WS ...
...
07:34:48 Starting up MyTool ...done.
Resuming build at Wed Dec 18 07:35:36 CET 2019 after Jenkins restart
Waiting to resume part of MyProject » MyProject-Pipeline 20191218-073417-rev4122d3ea: Finished waiting
[Pipeline] End of Pipeline
[lockable-resources] released lock on [MyTool#1, MyProject-Pipeline-mytool]
java.lang.ClassNotFoundException: org.jenkinsci.plugins.docker.workflow.Docker$Image
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:677)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:787)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:775)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:123)
at org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:104)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1022)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1355)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:220)
at org.jboss.marshalling.river.RiverUnmarshaller.readFields(RiverUnmarshaller.java:1853)
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title Reinhold Füreder commented on JENKINS-60513 Re: Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter The list of "hudson.plugins.git.GitSCM$DescriptorImpl" entries in "Manage Old Data" keeps growing; interestingly there is still only one for "hudson.scm.SubversionSCM$DescriptorImpl"... 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.203605.1576562327000.11204.1576647240133%40Atlassian.JIRA.
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title Reinhold Füreder commented on JENKINS-60513 Re: Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter IMHO caused by https://github.com/jenkinsci/jenkins/pull/4337 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.203605.1576562327000.11203.1576646940051%40Atlassian.JIRA.
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-60513
Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Change By:
Reinhold Füreder
After upgrading Jenkins core from v2.208 to v2.209 I see the following things that make me a bit nervous:* Start-up log{noformat}Running from: /usr/share/jenkins/jenkins.war2019-12-17 05:44:39.660+ [id=1] INFOorg.eclipse.jetty.util.log.Log#initialized: Logging initialized @373ms to org.eclipse.jetty.util.log.JavaUtilLog2019-12-17 05:44:39.761+ [id=1] INFOwinstone.Logger#logInternal: Beginning extraction from war file2019-12-17 05:44:40.758+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath2019-12-17 05:44:40.820+ [id=1] INFOorg.eclipse.jetty.server.Server#doStart: jetty-9.4.22.v20191022; built: 2019-10-22T13:37:13.455Z; git: b1e6b55512e008f7fbdf1cbea4ff8a6446d1073b; jvm 1.8.0_222-8u222-b10-1ubuntu1~16.04.1-b102019-12-17 05:44:41.192+ [id=1] INFOorg.eclipse.jetty.util.TypeUtil#: JVM Runtime does not support Modules2019-12-17 05:44:41.204+ [id=1] INFOo.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet2019-12-17 05:44:41.261+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node02019-12-17 05:44:41.261+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults2019-12-17 05:44:41.263+ [id=1] INFOo.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 60ms2019-12-17 05:44:41.604+ [id=1] INFOhudson.WebAppMain#contextInitialized: Jenkins home directory: /var/lib/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")2019-12-17 05:44:41.740+ [id=1] INFOo.e.j.s.handler.ContextHandler#doStart: Started w.@21422231{Jenkins v2.209,/,file:///var/cache/jenkins/war/,AVAILABLE}{/var/cache/jenkins/war}2019-12-17 05:44:41.770+ [id=1] INFOo.e.j.server.AbstractConnector#doStart: Started ServerConnector@3a12c404{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}2019-12-17 05:44:41.770+ [id=1] INFOorg.eclipse.jetty.server.Server#doStart: Started @2484ms2019-12-17 05:44:41.771+ [id=24]INFOwinstone.Logger#logInternal: Winstone Servlet Engine running: controlPort=disabled2019-12-17 05:44:42.936+ [id=30]INFOjenkins.InitReactorRunner$1#onAttained: Started initialization2019-12-17 05:44:42.943+ [id=29]INFOhudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last running version was 2.208. This Jenkins is version 2.209.2019-12-17 05:44:42.975+ [id=29]INFOhudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.208 to version 2.209. Loaded detached plugins (and dependencies): []2019-12-17 05:44:43.752+ [id=30]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2019-12-17 05:44:53.986+ [id=44]INFO
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title Reinhold Füreder commented on JENKINS-60513 Re: Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter Oops, I accidentally linked this issue with v2.208 (in https://jenkins.io/changelog/) and even "I had to rollback", whereas it should be linked with (still missing) v2.209 and maybe only "I experienced notable problems" instead: Sorry! 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.203605.1576562327000.9540.1576562520091%40Atlassian.JIRA.
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-60513
Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Change By:
Reinhold Füreder
After upgrading Jenkins core from v2.208 to v2.209 I see the following things that make me a bit nervous:* Start-up log{noformat}Running from: /usr/share/jenkins/jenkins.war2019-12-17 05:44:39.660+ [id=1] INFOorg.eclipse.jetty.util.log.Log#initialized: Logging initialized @373ms to org.eclipse.jetty.util.log.JavaUtilLog2019-12-17 05:44:39.761+ [id=1] INFOwinstone.Logger#logInternal: Beginning extraction from war file2019-12-17 05:44:40.758+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath2019-12-17 05:44:40.820+ [id=1] INFOorg.eclipse.jetty.server.Server#doStart: jetty-9.4.22.v20191022; built: 2019-10-22T13:37:13.455Z; git: b1e6b55512e008f7fbdf1cbea4ff8a6446d1073b; jvm 1.8.0_222-8u222-b10-1ubuntu1~16.04.1-b102019-12-17 05:44:41.192+ [id=1] INFOorg.eclipse.jetty.util.TypeUtil#: JVM Runtime does not support Modules2019-12-17 05:44:41.204+ [id=1] INFOo.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet2019-12-17 05:44:41.261+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node02019-12-17 05:44:41.261+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults2019-12-17 05:44:41.263+ [id=1] INFOo.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 60ms2019-12-17 05:44:41.604+ [id=1] INFOhudson.WebAppMain#contextInitialized: Jenkins home directory: /var/lib/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")2019-12-17 05:44:41.740+ [id=1] INFOo.e.j.s.handler.ContextHandler#doStart: Started w.@21422231{Jenkins v2.209,/,file:///var/cache/jenkins/war/,AVAILABLE}{/var/cache/jenkins/war}2019-12-17 05:44:41.770+ [id=1] INFOo.e.j.server.AbstractConnector#doStart: Started ServerConnector@3a12c404{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}2019-12-17 05:44:41.770+ [id=1] INFOorg.eclipse.jetty.server.Server#doStart: Started @2484ms2019-12-17 05:44:41.771+ [id=24]INFOwinstone.Logger#logInternal: Winstone Servlet Engine running: controlPort=disabled2019-12-17 05:44:42.936+ [id=30]INFOjenkins.InitReactorRunner$1#onAttained: Started initialization2019-12-17 05:44:42.943+ [id=29]INFOhudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last running version was 2.208. This Jenkins is version 2.209.2019-12-17 05:44:42.975+ [id=29]INFOhudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.208 to version 2.209. Loaded detached plugins (and dependencies): []2019-12-17 05:44:43.752+ [id=30]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2019-12-17 05:44:53.986+ [id=44]INFO
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-60513 Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-17 05:58 Priority: Critical Reporter: Reinhold Füreder After upgrading Jenkins core from v2.208 to v2.209 I see the following things that make me a bit nervous: Start-up log Running from: /usr/share/jenkins/jenkins.war 2019-12-17 05:44:39.660+ [id=1] INFOorg.eclipse.jetty.util.log.Log#initialized: Logging initialized @373ms to org.eclipse.jetty.util.log.JavaUtilLog 2019-12-17 05:44:39.761+ [id=1] INFOwinstone.Logger#logInternal: Beginning extraction from war file 2019-12-17 05:44:40.758+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath 2019-12-17 05:44:40.820+ [id=1] INFOorg.eclipse.jetty.server.Server#doStart: jetty-9.4.22.v20191022; built: 2019-10-22T13:37:13.455Z; git: b1e6b55512e008f7fbdf1cbea4ff8a6446d1073b; jvm 1.8.0_222-8u222-b10-1ubuntu1~16.04.1-b10 2019-12-17 05:44:41.192+ [id=1] INFOorg.eclipse.jetty.util.TypeUtil#: JVM Runtime does not support Modules 2019-12-17 05:44:41.204+ [id=1] INFOo.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet 2019-12-17 05:44:41.261+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0 2019-12-17 05:44:41.261+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults 2019-12-17 05:44:41.263+ [id=1] INFO
[JIRA] (JENKINS-60434) "Prepare for shutdown" should continue executing already running pipelines to completion
Title: Message Title Reinhold Füreder commented on JENKINS-60434 Re: "Prepare for shutdown" should continue executing already running pipelines to completion Thomas de Grenier de Latour Thanks for the insight! And wow, that is impressive and I am not sure you got that right in the first attempt 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.203506.1576045591000.5331.1576068900522%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Reinhold Füreder commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Thanks again Devin Nusbaum! And following your advice => JENKINS-60434 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.169794.1460663849000.4879.1576045681428%40Atlassian.JIRA.
[JIRA] (JENKINS-60434) "Prepare for shutdown" should continue executing already running pipelines to completion
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-60434 "Prepare for shutdown" should continue executing already running pipelines to completion Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-12-11 06:26 Priority: Major Reporter: Reinhold Füreder Based on Devin Nusbaum's comment from JENKINS-34256: A fix for this issue was just released in Pipeline: Groovy Plugin version 2.78. I think there is/was some confusion as to the expected behavior (myself included!), so let me try to clarify: When Jenkins prepares for shutdown, all running Pipelines are paused, and this is the intended behavior. The unintended behavior was that if you canceled shutdown, Pipelines remained paused. This has been fixed in 2.78; Pipelines will now resume execution if shutdown is canceled. Before 2.78, you had to manually pause and unpause each Pipeline to get it to resume execution, or restart Jenkins. Additionally, preparing Jenkins for shutdown and canceling shutdown now each cause a message to be printed to Pipeline build logs indicating that the Pipeline is being paused or resumed due to shutdown so that it is easier to understand what is happening. Based on comments here and elsewhere, I think some users would prefer a variant of "Prepare for shutdown" in which Pipelines continue executing to completion, the same as other types of jobs like Freestyle. If that is something you want, please open a new ticket, describing your use case and the desired behavior. [...] If there is some other aspect of this issue that you would like to see addressed, or a different behavior you would prefer, please open a new ticket describing your
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Reinhold Füreder commented on JENKINS-60393 Re: cloudbees-folder circular dependency Naive question: My Jenkins server was starting up fine => is downgrading strictly necessary so that "Folder" job etc is working? 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.203447.1575664332000.4875.1576043880428%40Atlassian.JIRA.
[JIRA] (JENKINS-60411) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface.
Title: Message Title Reinhold Füreder commented on JENKINS-60411 Re: Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. Duplicate of JENKINS-60393, I guess 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.203468.1575917826000.4865.1576043760178%40Atlassian.JIRA.
[JIRA] (JENKINS-60411) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface.
Title: Message Title Reinhold Füreder commented on JENKINS-60411 Re: Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. After updating some plugins (cloudbees-folder:6.10.0, branch-api:2.5.5, workflow-api:2.38) and restarting afterwards => naively guessing "cloudbees-folder:6.10.0" (from v6.9) is the culprit: ... 2019-12-11 05:43:27.054+ [id=36]INFOjenkins.InitReactorRunner$1#onAttained: Started all plugins 2019-12-11 05:43:27.505+ [id=33]INFOh.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping 2019-12-11 05:43:27.520+ [id=33]INFOh.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping 2019-12-11 05:43:27.521+ [id=33]WARNING h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate Key[type=com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:194) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.iterator(ExtensionList.java:172) at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.(AbstractFolderConfiguration.java:36) at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration$$FastClassByGuice$$2295d22e.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32) at
[JIRA] (JENKINS-60411) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface.
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-60411 Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. Change By: Reinhold Füreder Component/s: cloudbees-folder-plugin 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.203468.1575917826000.4859.1576043640294%40Atlassian.JIRA.
[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Reinhold Füreder commented on JENKINS-58878 Re: withCredentials hangs Thanks, this is very promising/good news! 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.201211.1565374229000.1584.1575556920552%40Atlassian.JIRA.
[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Reinhold Füreder commented on JENKINS-58878 Re: withCredentials hangs Devin Nusbaum By any chance could this fix also solve my sporadically experienced hanging pipelines in withDockerRegistry/withDockerServer context (with executor on Jenkins master *cough*)? Example thread dump: at DSL.withDockerRegistry(not currently scheduled, or running blocks) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(Docker.groovy:40) at DSL.withEnv(Native Method) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(Docker.groovy:39) at org.jenkinsci.plugins.docker.workflow.Docker.node(Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(Docker.groovy:38) at com.acme.php.phpstorm.OfflineInspection.execute(OfflineInspection.groovy:59) at acme.executePhpStormInspections(acme.groovy:256) at WorkflowScript.run(WorkflowScript:101) ... Please note, however, that it appeared as if the single or first (?) step inside such withDockerRegistry/withDockerServer contexts may sometimes actually be still executed... 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
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title
Reinhold Füreder commented on JENKINS-34256
Re: Preparing Jenkins For Shutdown Hangs Running Pipelines
Devin Nusbaum Thanks, I think that ("The main change in my PR is that today, if you cancel shutdown after clicking "Prepare for shutdown", the Pipeline builds stay paused. You have to manually pause and unpause the builds to get them to resume or restart Jenkins. After my PR, canceling shutdown will unpause the builds and resume them automatically.") should actually really address one of my (many months ago) experienced problems in this concern! (Because I have a groovy init hook script that always configures Jenkins to start in so-called quiet mode...) As other users more or less diplomatically commented, there is still room for related important enhancements: maybe these can be collected and discussed and prioritised and addressed in another future sprint/story? (And I think Jenkins is still in massive use nowadays and hopefully not dead for a long time...)
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.169794.1460663849000.1208.1575531361659%40Atlassian.JIRA.
[JIRA] (JENKINS-59913) Missing change log entry for (buggy) version v1.31
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-59913 Missing change log entry for (buggy) version v1.31 Issue Type: Task Assignee: Unassigned Components: durable-task-plugin Created: 2019-10-24 06:25 Priority: Minor Reporter: Reinhold Füreder See e.g. JENKINS-59903, JENKINS-59906 and JENKINS-59907 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Reinhold Füreder commented on JENKINS-59903
Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Also a problem when running Jenkins not in Docker and executing pipeline on Jenkins master (=> psst!); problem is definitely caused by new "Durable Task" plugin v1.31 bug:
Latest version of Jenkins core (v2.201) running on Ubuntu 16.04
The logs seem to indicate the problem already appears when trying to start the Docker container in the pipeline, but maybe the logs are just mangled?
See "// !!!" comment in belows build log...
Build log (proprietary):
...
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (linkchecker)
[Pipeline] script
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withDockerRegistry
[Pipeline] {
[Pipeline] isUnix
[Pipeline] sh
06:37:20 + docker inspect -f . ACME/linkchecker:5
06:37:20
06:37:20 Error: No such object: ACME/linkchecker:5
06:37:20 06:37:20.408218 durable_task_monitor.go:63: exit status 1 // !!!
[Pipeline] isUnix
[Pipeline] sh
06:37:20 + docker inspect -f . dockerregistry.ACME.com/ACME/linkchecker:5
06:37:20 .
[Pipeline] withDockerContainer
06:37:20 Jenkins does not seem to be running inside a container
06:37:20 $ docker run -t -d -u 10112:10005 -w /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline -v /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline:/var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline:rw,z -v /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline@tmp:/var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e dockerregistry.ACME.com/ACME/linkchecker:5 cat
06:37:21 $ docker top 39f784ea27cbf6593fd40c1faaf04948daae94e97eb8ba42517f7c2f5e40c21e -eo pid,comm
[Pipeline] {
[Pipeline] sh
06:42:27 process apparently never started in /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline@tmp/durable-aed939a9 // !!!
06:42:27 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
[Pipeline] }
...
ERROR: script returned exit code -2
Finished: FAILURE
Pipeline code (in shared Jenkins pipeline library):
...
void
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-59907
Re: sh steps stuck indefinitely after upgrading durable-task to v1.31
I think this issue's title is just one of the symptoms of the new "Durable Task" plugin v1.31 bug:* Latest version of Jenkins core (v2.201) running on Ubuntu 16.04* In on of our pipelines we do not use Docker at all and just exeucte an "sh" step (on Jenkins master :-( => psst!) via ssh on another server and it fails right away:* Pipeline code:{code}...boolean skipRenewal = truescript.xortex.skipableStage("check need for renewal") {def exitCode = script.sh(returnStatus: true, script: makeRenewLocalCertShellCmd(config.domainName)) // ! This is line 54 where the exception happens...private static String makeRenewLocalCertShellCmd(String domainName) { return "ssh -t -t MyServer.ACME.com './renewlocalcert ${domainName}'"}{code}* Build log (proprietary) with nice exception stacktrace at the end:{code}...[Pipeline] // stage[Pipeline] stage[Pipeline] { (check need for renewal)[Pipeline] sh[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] ansiColor[Pipeline] {[Pipeline] echo06:37:13 Pipeline problem: Build failed (check need for renewal) due to: "java.io.IOException: Cannot run program "/var/lib/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64" (in directory "/var/lib/jenkins/workspace/Sandbox/ACME.renewCerts"): error=13, Permission denied" => Please check the "Console/Log Output" => Failure notification will be sent..java.io.IOException: error=13, Permission denied at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:230) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)Caused: java.io.IOException: Cannot run program "/var/lib/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64" (in directory "/var/lib/jenkins/workspace/Sandbox/ACME.renewCerts"): error=13, Permission denied at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:230) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286)
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title
Reinhold Füreder commented on JENKINS-59907
Re: sh steps stuck indefinitely after upgrading durable-task to v1.31
I think this issue's title is just one of the symptoms of the new "Durable Task" plugin v1.31 bug:
In on of our pipelines we do not use Docker at all and just exeucte an "sh" step (on Jenkins master => psst!) via ssh on another server and it fails right away:
Pipeline code:
...
boolean skipRenewal = true
script.xortex.skipableStage("check need for renewal") {
def exitCode = script.sh(returnStatus: true, script: makeRenewLocalCertShellCmd(config.domainName)) // ! This is line 54 where the exception happens
...
private static String makeRenewLocalCertShellCmd(String domainName) {
return "ssh -t -t MyServer.ACME.com './renewlocalcert ${domainName}'"
}
Build log (proprietary) with nice exception stacktrace at the end:
...
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (check need for renewal)
[Pipeline] sh
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] ansiColor
[Pipeline] {
[Pipeline] echo
06:37:13 Pipeline problem: Build failed (check need for renewal) due to: "java.io.IOException: Cannot run program "/var/lib/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64" (in directory "/var/lib/jenkins/workspace/Sandbox/ACME.renewCerts"): error=13, Permission denied" => Please check the "Console/Log Output" => Failure notification will be sent...
...
java.io.IOException: error=13, Permission denied
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
at hudson.Proc$LocalProc.(Proc.java:250)
at hudson.Proc$LocalProc.(Proc.java:219)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:937)
at hudson.Launcher$ProcStarter.start(Launcher.java:455)
at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:230)
at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)
Caused: java.io.IOException: Cannot run program
[JIRA] (JENKINS-51287) Stage view overlaps test overview
Title: Message Title Reinhold Füreder commented on JENKINS-51287 Re: Stage view overlaps test overview I think this has been fixed some time ago 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.190621.1526284437000.7977.1571145900322%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Olivier Lamy Sorry for my delayed feedback: AFAIK (no user complaints in my company – at least none that I know of...) the snapshot build of sse-gateway worked fine; and on Jenkins server neither remaining "EventDispatcher.retryProcessor" threads, nor thousands of them at the same time. => Looks good 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.200967.156416397.2452.1567057680422%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder edited a comment on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I am pretty sure to have stumbled over this issue as well (using sse-gateway v1.19) today: * there are sometimes more than 1000 threads with name "EventDispatcher.retryProcessor", then again "just" ~250 * and one pipeline build (on Jenkins master – yes, I know this is an antipattern) failed with "unable to create new native thread" (in Jenkins docker plugin leading to remaining Docker container) * (actually yesterday occurred another weird problem that I have not experienced before, namely a hanging pipeline; but I just killed it instead of trying to get a java stacktrace, so I don't really know if it is related to this issue here) * interestingly I updated to this version already on 2019-08-02** but I updated Jenkins (core) yesterday (2019-08-20) late afternoon to 2.190 (from 2.189); and a few minutes later also two Jenkins Plugins: "pubsub-light" to 1.13 (from 1.12); and presumably very innocent "github-branch-source" [~dnusbaum]/[~olamy] * => What is the current (workaround) recommendation? * * trying to install the latest snapshot from [https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/sse-gateway/1.20-SNAPSHOT/]?I have now (cleaned up) and restarted Jenkins => not a single thread with name "EventDispatcher.retryProcessor" is initially around 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.200967.156416397.7609.1566453600938%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Sverre Moe Ad "cleaned up": Sorry for my lack of clarity => due to the OOM there were remaining running Docker Containers that I had to stop and remove; and it also appeared that about 2xx "EventDispatcher.retryProcessor" threads were remaining inside Jenkins Java process... Other notes (~15h after Jenkins master restart): This morning no "EventDispatcher.retryProcessor" threads are there (or remaining) yet. Interestingly there are 25 "org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep" threads, even though just one pipeline build is running (without any parallelism) 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.200967.156416397.7580.1566453540437%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder edited a comment on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I am pretty sure to have stumbled over this issue as well (using sse-gateway v1.19) today: * there are sometimes more than 1000 threads with name "EventDispatcher.retryProcessor", then again "just" ~250 * and one pipeline build (on Jenkins master – yes, I know this is an antipattern) failed with "unable to create new native thread" (in Jenkins docker plugin leading to remaining Docker container) * (actually yesterday occurred another weird problem that I have not experienced before, namely a hanging pipeline; but I just killed it instead of trying to get a java stacktrace, so I don't really know if it is related to this issue here) * ( interestingly I updated to this version already on 2019-08-02 ** but I updated Jenkins (core ) yesterday (2019-08-20) late afternoon to 2.190 (from 2.189); and a few minutes later also two Jenkins Plugins: "pubsub-light" to 1.13 (from 1.12); and presumably very innocent "github-branch-source" => What is the current recommendation? * trying to install the latest snapshot from [https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/sse-gateway/1.20-SNAPSHOT/]?I have now (cleaned up) and restarted Jenkins => not a single thread with name "EventDispatcher.retryProcessor" is initially around 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.200967.156416397.7114.1566399900822%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder edited a comment on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I am pretty sure to have stumbled over this issue as well (using sse-gateway v1.19) today: * there are sometimes more than 1000 threads with name "EventDispatcher.retryProcessor" , then again "just" ~250 * and one pipeline build (on Jenkins master – yes, I know this is an antipattern) failed with "unable to create new native thread" (in Jenkins docker plugin leading to remaining Docker container) * (actually yesterday occurred another weird problem that I have not experienced before, namely a hanging pipeline; but I just killed it instead of trying to get a java stacktrace, so I don't really know if it is related to this issue here) * (interestingly I updated to this version already on 2019-08-02)=> What is the current recommendation? * trying to install the latest snapshot from [https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/sse-gateway/1.20-SNAPSHOT/]? I have now (cleaned up) and restarted Jenkins => not a single thread with name "EventDispatcher.retryProcessor" is initially around 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.200967.156416397.7097.1566399240475%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I am pretty sure to have stumbled over this issue as well (using sse-gateway v1.19) today: there are sometimes more than 1000 threads with name "EventDispatcher.retryProcessor" and one pipeline build (on Jenkins master – yes, I know this is an antipattern) failed with "unable to create new native thread" (in Jenkins docker plugin leading to remaining Docker container) (actually yesterday occurred another weird problem that I have not experienced before, namely a hanging pipeline; but I just killed it instead of trying to get a java stacktrace, so I don't really know if it is related to this issue here) (interestingly I updated to this version already on 2019-08-02) => What is the current recommendation? trying to install the latest snapshot from https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/sse-gateway/1.20-SNAPSHOT/? 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.200967.156416397.7019.1566397680867%40Atlassian.JIRA.
[JIRA] (JENKINS-58673) System.out "GOT CONTEXT FOR " remainders in jenkins log
Title: Message Title Reinhold Füreder commented on JENKINS-58673 Re: System.out "GOT CONTEXT FOR " remainders in jenkins log Devin Nusbaum Thanks! 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.200955.1564132534000.3674.1564461240169%40Atlassian.JIRA.
[JIRA] (JENKINS-58671) Concurrency problems with SVN workflow libs => maybe upgrade MapDB
Title: Message Title Reinhold Füreder commented on JENKINS-58671 Re: Concurrency problems with SVN workflow libs => maybe upgrade MapDB Also seen: 2019-07-26 11:40:35.928+ [id=152] WARNING j.s.i.s.SVNRepositoryView#: failing to make/load /var/jenkins_home/caches/svn-fa86427e-e420-4d14-a4fd-9ab1bdfcde57.db java.io.IOException: storage has invalid header Caused: java.io.IOError at org.mapdb.StoreDirect.checkHeaders(StoreDirect.java:254) at org.mapdb.StoreWAL.checkHeaders(StoreWAL.java:115) at org.mapdb.StoreDirect.(StoreDirect.java:207) at org.mapdb.StoreWAL.(StoreWAL.java:74) at org.mapdb.DBMaker.extendStoreWAL(DBMaker.java:981) at org.mapdb.DBMaker.makeEngine(DBMaker.java:758) at org.mapdb.DBMaker.make(DBMaker.java:701) at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:105) at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:338) at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:294) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:636) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.lambda$retrieve$0(SCMSourceRetriever.java:89) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrySCMOperation(SCMSourceRetriever.java:104) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:89) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:138) at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:125) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)
[JIRA] (JENKINS-58673) System.out "GOT CONTEXT FOR " remainders in jenkins log
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-58673 System.out "GOT CONTEXT FOR " remainders in jenkins log Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-07-26 09:15 Environment: I think/hope latest and greatest versions Priority: Minor Reporter: Reinhold Füreder E.g.: ... GOT CONTEXT FOR init GOT CONTEXT FOR linkchecker ... Seems to happen in some declarative pipelines IIRC Devin Nusbaum (once again I am sorry if I mix things up) actually fixed that somewhere (in a Jenkins plugin) already (a few weeks or mabe very few months ago), but presumably there was no release of the Jenkins plugin since then (or I unfortunately and surprisingly do not use the latest version of that plugin)? Hint: This log is mentioned in a comment from June (see JENKINS-55038) as well...
[JIRA] (JENKINS-58671) Concurrency problems with SVN workflow libs => maybe upgrade MapDB
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-58671 Concurrency problems with SVN workflow libs => maybe upgrade MapDB Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: mapdb-api-plugin, subversion-plugin Created: 2019-07-26 08:47 Environment: Everything relevant is latest and greatest; Jenkins in Docker Priority: Minor Reporter: Reinhold Füreder Initial Docker based Jenkins startup based on JCasC and job-dsl and pipeline jobs auto-scheduled (via job-dsl 'queue' command) right after their creation that all use a shared Jenkins pipeline library in SVN. This did not hurt and led to successful pipeline job executions 2019-07-26 08:16:12.952+ [id=150] WARNING j.s.i.s.SVNRepositoryView#: failing to make/load /var/jenkins_home/caches/svn-fa86427e-e420-4d14-a4fd-9ab1bdfcde57.db java.lang.AssertionError: unknown trans log instruction '-58' at log offset: 176 at org.mapdb.StoreWAL.replayLogFile(StoreWAL.java:827) at org.mapdb.StoreWAL.commit(StoreWAL.java:606) at org.mapdb.EngineWrapper.commit(EngineWrapper.java:94) at org.mapdb.DBMaker.makeEngine(DBMaker.java:838) at org.mapdb.DBMaker.make(DBMaker.java:701) at jenkins.scm.impl.subversion.SVNRepositoryView.(SVNRepositoryView.java:105) at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:338) at
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Reinhold Füreder commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Devin Nusbaum Sorry, I guess you are right => I'll adapt the issue links 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.200110.1560887329000.924.1564063860375%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Reinhold Füreder edited a comment on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" We are also experiencing this *huge problem* (but not all the time though!?) – but are hesitating to downgrade, as 1.17 contains one really, really helpful new feature: https://issues.jenkins JENKINS - ci.org/browse/ 39203 ([~dnusbaum] Based on the BlueOcean changelog one naively assumes that this issue is actually caused by JENKINS-39203 => therefore I naively linked this issues) 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.200110.1560887329000.823.1564055702489%40Atlassian.JIRA.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Reinhold Füreder commented on JENKINS-50561 Re: Add @Symbol to "throttle builds" job properties (I can confirm that it is not working and just silently ignored ) 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.189630.1522823307000.1621.1562228460436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Reinhold Füreder edited a comment on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" We are also experiencing this *huge problem* -- ( but not all the time though!?) – but are hesitating to downgrade, as 1.17 contains one really, really helpful new feature: https://issues.jenkins-ci.org/browse/JENKINS-39203 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.200110.1560887329000.775.1562149380402%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Reinhold Füreder commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" We are also experiencing this huge problem – but are hesitating to downgrade, as 1.17 contains one really, really helpful new feature: https://issues.jenkins-ci.org/browse/JENKINS-39203 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.200110.1560887329000.487.1562136180220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title Reinhold Füreder commented on JENKINS-57579 Re: New "unstable" step is not visualizing stage as unstable Thanks: it works like a charm! 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.199495.1558434359000.25912.1560337740182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title Reinhold Füreder commented on JENKINS-57579 Re: New "unstable" step is not visualizing stage as unstable Pipeline Graph Analysis Plugin: 1.10 Blue Ocean: 1.16.0 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.199495.1558434359000.10343.1558624500129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57599) (Question) Jenkins logs in UTC since 2.177
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-57599 (Question) Jenkins logs in UTC since 2.177 Issue Type: Task Assignee: Jesse Glick Components: core, winstone-jetty Created: 2019-05-22 10:05 Priority: Trivial Reporter: Reinhold Füreder In the past I had configured Jenkins log format via Java system property, this is starting from Jenkins v2.177 thanks to https://github.com/jenkinsci/winstone/pull/63 no more necessary (and also no more taken into account or overridden – which is OK). Turning now to my question, however: I was wondering, if hard-coding the timezone for Jenkins server logs to UTC is really on purpose or not, or is good or bad? (cf. https://github.com/jenkinsci/support-core-plugin/commit/8f35dd1ad5e0c5e498e5579bcf6671f11bf6d3c7#diff-046257f44dc4c390341c1e16a4b4e42c) Of course it only makes a difference for humans looking at the log lines, because any log analysis software or central logging will convert it correctly anyhow. And frankly I also have no proper opinion on whether this is good or bad: I just noticed the difference and was irritated... Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Reinhold Füreder commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Devin Nusbaum Please see https://issues.jenkins-ci.org/browse/JENKINS-57579 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.175630.1477271041000.6714.1558434486830%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Reinhold Füreder edited a comment on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should [~dnusbaum] Please see https://issues.jenkins-ci.org/browse/ JENKINS-57579 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.175630.1477271041000.6944.1558434489472%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-57579
New "unstable" step is not visualizing stage as unstable
Change By:
Reinhold Füreder
From JENKINS-39203Minimal (scripted) pipeline via (e.g. "Pipeline script" of a new job of type "Pipeline"):{code:java}stage('stage') { echo('In stage "stage"...')}stage('unstable stage') {unstable 'my message for unstable'}{code}The build log is as expected:{noformat}[Pipeline] Start of Pipeline[Pipeline] stage[Pipeline] { (stage)[Pipeline] echoIn stage "stage"...[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (unstable stage)[Pipeline] unstableWARNING: my message for unstable[Pipeline] }[Pipeline] // stage[Pipeline] End of PipelineFinished: UNSTABLE{noformat}This leads to the stage "unstable stage" rendered wrongly as being successful: !image-2019-05-21-12-22-43-337.png|thumbnail!
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.199495.1558434359000.6711.1558434420168%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title
Reinhold Füreder created an issue
Jenkins / JENKINS-57579
New "unstable" step is not visualizing stage as unstable
Issue Type:
Bug
Assignee:
Devin Nusbaum
Attachments:
image-2019-05-21-12-22-43-337.png
Components:
pipeline
Created:
2019-05-21 10:25
Priority:
Critical
Reporter:
Reinhold Füreder
From JENKINS-39203 Minimal (scripted) pipeline via (e.g. "Pipeline script" of a new job of type "Pipeline"):
stage('stage') {
echo('In stage "stage"...')
}
stage('unstable stage') {
unstable 'my message for unstable'
}
The build log is as expected:
[Pipeline] Start of Pipeline
[Pipeline] stage
[Pipeline] { (stage)
[Pipeline] echo
In stage "stage"...
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (unstable stage)
[Pipeline] unstable
WARNING: my message for unstable
[Pipeline] }
[Pipeline] // stage
[Pipeline] End of Pipeline
Finished: UNSTABLE
This leads to the stage "unstable stage" rendered wrongly as being successful:
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
Hm, while it seems to work fine for {{junit}} steps like in the screenshot !image-2019-05-17-16-18-02-806.png|thumbnail! it does not visualize the unstable stage when using code like [~hugo_l] (in a replayed scripted pipeline): !screenshot-not-showing-unstable-stage.png|thumbnail!How comes!?
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.175630.1477271041000.6480.1558433704128%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Reinhold Füreder commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Hm, while it seems to work fine for junit steps like in the screenshot it does not visualize the unstable stage when using code like Hugo L (in a replayed pipeline): How comes!? 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.175630.1477271041000.2724.1558090865320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Reinhold Füreder Attachment: screenshot-not-showing-unstable-stage.png 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.175630.1477271041000.2477.1558090746542%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57074) Version 2.173 creates tmp-files and doesn't delete them
Title: Message Title Reinhold Füreder updated JENKINS-57074 According to Reiner Wirtz this is not caused by Jenkins Jenkins / JENKINS-57074 Version 2.173 creates tmp-files and doesn't delete them Change By: Reinhold Füreder Status: Open Fixed but Unreleased Resolution: Won't Do 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-57074) Version 2.173 creates tmp-files and doesn't delete them
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-57074
Version 2.173 creates tmp-files and doesn't delete them
Change By:
Reinhold Füreder
SInce -Since I updated jenkins from 2.172 to 2.173 my tmp-filesystem filled with about 75 GB of files, owned by the user jenkins, who started the process jenkins, and filled all my space on the /tmp filesystem during my nightly tests with about 20 slaves. - - The names are always like "jar_cache*.tmp" - - When the filesystem has been filled, jenkins stops - {color:#de350b} Please delete this issue, it looks there is a test application that creates the files {color}
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-57074) Version 2.173 creates tmp-files and doesn't delete them
Title: Message Title Reinhold Füreder commented on JENKINS-57074 Re: Version 2.173 creates tmp-files and doesn't delete them Based on the update of this issue's description by Reiner Wirtz I try to do as much as I (as a naive user) can do... Unfortunately I have no idea how https://jenkins.io/changelog/ can be cleaned of refering to this issue... 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Reinhold Füreder edited a comment on JENKINS-47286 Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view Assigning this back to you [~michaelneale] with the update/summary comment above ... 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Reinhold Füreder assigned an issue to Michael Neale Assigning this back to you with update/summary comment... Jenkins / JENKINS-47286 Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view Change By: Reinhold Füreder Assignee: Reinhold Füreder Michael Neale 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Reinhold Füreder commented on JENKINS-47286 Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view Michael Neale I am a bit surprised by being the new assignee of this issue, as I am not sure what you are expecting from me. Considering the admittedly rather long history of this issue and its distractions/deviations I think I can only try to do a little update: the issue's title/goal is still completely the same and correct and IMHO the "only" (or main) thing certainly missing is a stable/public API for org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME) (as this is annotated with @Restricted(NoExternalUse.class)) In the course of doing that other questions from https://issues.jenkins-ci.org/browse/JENKINS-47286?focusedCommentId=334032=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-334032 might be answered as well... (I think item #2 "mouse hover" was actually fixed; see https://issues.jenkins-ci.org/browse/JENKINS-47286?focusedCommentId=360479=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360479) 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-44869) Activity tabs Run id column should expand to fit value
Title: Message Title Reinhold Füreder commented on JENKINS-44869 Re: Activity tabs Run id column should expand to fit value Michael Neale Sorry for the confusion. I referred to Gavin Mogan's comment and JENKINS-46521 Mock up: Now/old: Future/new: 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-44869) Activity tabs Run id column should expand to fit value
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-44869 Activity tabs Run id column should expand to fit value Change By: Reinhold Füreder Attachment: screenshot-future.png 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-44869) Activity tabs Run id column should expand to fit value
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-44869 Activity tabs Run id column should expand to fit value Change By: Reinhold Füreder Attachment: screenshot-now.png 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-39343) Persistent search/overviews/filtered views
Title: Message Title Reinhold Füreder commented on JENKINS-39343 Re: Persistent search/overviews/filtered views Naive food for thoughts: Jenkins admins have to use Classic UI anyways, and that is OK. By contrast Jenkins users (= developers) can/shall use nice/modern/new Blue Ocean UI for everything the need (so failure notifications always link primarily to BO) and they do NOT need the overview (like Jenkins admins)? So I can perfectly live with this issue being closed – of course assuming that (Cloud Bees) Jenkins development resources are then spent on more vital things like the following https://issues.jenkins-ci.org/browse/JENKINS-44869 https://issues.jenkins-ci.org/browse/JENKINS-47286 https://issues.jenkins-ci.org/browse/JENKINS-46715 https://issues.jenkins-ci.org/browse/JENKINS-46521 https://issues.jenkins-ci.org/browse/JENKINS-39203 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Reinhold Füreder commented on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
While I am not sure if this is the correct/perfect/recommended place for this question, it admittedly fits to this issue and I can actually give you a little hint My approach for this is to have a skipableStage step in my shared Jenkins pipeline library that wraps the default/standard stage step, so the usage is almost like normally:
...
acmeSharedLibrary.skipableStage("stage name") {
... // normal stage implementation
}
...
... and the steps implementation in pseudo code is:
stage(stageName) {
if (currentBuild.result) {
echo "Skipping stage '${stageName}' due to build result '${currentBuild.result}'..."
Result result = Result.fromString(currentBuild.result)
markStageSkippedForResult(stageName, result) // via the aformentioned workaround
} else {
body() // which is the closure block of this "skippableStage"
}
}
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-54997) Deprecated calls to Run.getLogFile
Title: Message Title Reinhold Füreder commented on JENKINS-54997 Re: Deprecated calls to Run.getLogFile Naive thought: Can it be that a potential fix might "solely" require: Remove the call (https://github.com/jenkinsci/email-ext-plugin/blob/287ed8955bfddd424ba5252c11a36cc9c0327407/src/main/java/hudson/plugins/emailext/AttachmentUtils.java#L200), as the result is not used any further Because in inner class LogFileDataSource the correct replacement getLogText() according to JENKINS-54128 is already used (mostly) Replace the call in https://github.com/jenkinsci/email-ext-plugin/blob/287ed8955bfddd424ba5252c11a36cc9c0327407/src/main/java/hudson/plugins/emailext/AttachmentUtils.java#L111 with a hard-coded "text/plain" (maybe there is a const or whatever) Because it is always just a text file This is also the "(mostly)" in the first problem 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-54997) Deprecated calls to Run.getLogFile
Title: Message Title Reinhold Füreder commented on JENKINS-54997 Re: Deprecated calls to Run.getLogFile Naive thought: Can it be that a potential fix might "solely" require: Remove the call (https://github.com/jenkinsci/email-ext-plugin/blob/287ed8955bfddd424ba5252c11a36cc9c0327407/src/main/java/hudson/plugins/emailext/AttachmentUtils.java#L200), as the result is not used any further Because in inner class LogFileDataSource the correct replacement getLogText() according to JENKINS-54128 is already used (mostly) Replace the call in https://github.com/jenkinsci/email-ext-plugin/blob/287ed8955bfddd424ba5252c11a36cc9c0327407/src/main/java/hudson/plugins/emailext/AttachmentUtils.java#L111 with a hard-coded "text/plain" (maybe there is a const or whatever) Because it is always just a text file This is also the "(mostly)" in the first problem 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-44869) Activity tabs Run id column should expand to fit value
Title: Message Title Reinhold Füreder commented on JENKINS-44869 Re: Activity tabs Run id column should expand to fit value Oh yes, this sounds like a great idea: hiding the "Commit" column for a non-multi branch pipeline in favour of showing the full build display number in the BO's activity tab "Run" id column (see JENKINS-44869) would be ideal/fine for me because I have the commit ID (SVN revision or shortened GIT commit hash) as suffix of my therefore quite long build display number, e.g. "20170613-161100-rev134098" (i.e. "--rev") 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-46521) Non-multibranch pipelines do not have any changeset information
Title: Message Title Reinhold Füreder commented on JENKINS-46521 Re: Non-multibranch pipelines do not have any changeset information Thanks for the insider/background information (and the hint in JENKINS-44869): well, yes, actually I (therefore) have the commit ID (SVN revision or shortened GIT commit hash) as suffix of my therefore quite long build display number, e.g. "20170613-161100-rev134098" (i.e. "--rev") and thus hiding the "Commit" column for a non-multi branch pipeline in favour of showing the full build display number in the BO's activity tab "Run" id column (see JENKINS-44869) would be ideal/fine for me 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-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Reinhold Füreder commented on JENKINS-5 Re: Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab Stuart Rowe and Gavin Mogan: Sorry for the confusion. I am really extremely pretty sure that the problem I described in https://issues.jenkins-ci.org/browse/JENKINS-5?focusedCommentId=343321=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-343321 (with rather straightforward reproducer steps) works now as expected (for "changes" AND for "tests") – and I think that was really the same problem as this issue's original description. However, I could also imagine that Stuart Rowe is perfectly right about that he only fixed the "changes" now in the course of JENKINS-55497, and "tests" was already fixed some time ago... 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.
