[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Edward Yang commented on JENKINS-50019 Re: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer The agents run a variety of different configurations, but this particular failure https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-win-ws2016-cuda9-cudnn7-py3-build/3541//console occurred on a Windows machine whose Java was installed via choco. This Java is jdk1.8.0_162 from https://chocolatey.org/packages/jdk8 In comparison, the server is running stock openjdk version "1.8.0_151" from Ubuntu Xenial. I can try to dig up other versions if that would be helpful. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49210) Do not use ArrayList#sublist()
Title: Message Title ikedam closed an issue as Fixed Released in extensible-choice-paramter-1.5.0 Jenkins / JENKINS-49210 Do not use ArrayList#sublist() Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22316) Filter options by input
Title: Message Title ikedam closed an issue as Fixed Released in extensible-choice-paramter-1.5.0 Jenkins / JENKINS-22316 Filter options by input Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49210) Do not use ArrayList#sublist()
Title: Message Title ikedam updated JENKINS-49210 Jenkins / JENKINS-49210 Do not use ArrayList#sublist() Change By: ikedam Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22316) Filter options by input
Title: Message Title ikedam resolved as Fixed Jenkins / JENKINS-22316 Filter options by input Change By: ikedam Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22316) Filter options by input
Title: Message Title ikedam commented on JENKINS-22316 Re: Filter options by input https://github.com/jenkinsci/extensible-choice-parameter-plugin/pull/35 https://github.com/jenkinsci/extensible-choice-parameter-plugin/pull/36 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49017) configSubmit exception with Textarea choices ended with empty line
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49017 Re: configSubmit exception with Textarea choices ended with empty line Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/utility/TextareaStringListUtility.java src/main/resources/META-INF/hudson.remoting.ClassFilter src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinitionJenkinsTest.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest.java src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jobs/JobWithSublist/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider.xml http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/c009a1c9b10071ca5457707491424f261dfbb4c6 Log: Merge pull request #37 from ikedam/feature/JENKINS-49210_NoSublist JENKINS-49210 JENKINS-49017 Do not use RandomAccessSubList Compare: https://github.com/jenkinsci/extensible-choice-parameter-plugin/compare/584197ec252e...c009a1c9b100 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-49210) Do not use ArrayList#sublist()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49210 Re: Do not use ArrayList#sublist() Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/utility/TextareaStringListUtility.java src/main/resources/META-INF/hudson.remoting.ClassFilter src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinitionJenkinsTest.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest.java src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jobs/JobWithSublist/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider.xml http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/c009a1c9b10071ca5457707491424f261dfbb4c6 Log: Merge pull request #37 from ikedam/feature/JENKINS-49210_NoSublist JENKINS-49210 JENKINS-49017 Do not use RandomAccessSubList Compare: https://github.com/jenkinsci/extensible-choice-parameter-plugin/compare/584197ec252e...c009a1c9b100 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49017) configSubmit exception with Textarea choices ended with empty line
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49017 Re: configSubmit exception with Textarea choices ended with empty line Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/utility/TextareaStringListUtility.java src/main/resources/META-INF/hudson.remoting.ClassFilter src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinitionJenkinsTest.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest.java src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jobs/JobWithSublist/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider.xml http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/afa9f3236d668a427cbcb8e504b32fc59af26dfb Log: [FIXED JENKINS-49210] JENKINS-49017 Do not use RandomAccessSubList As fix for JEP-200. Unfortunately I have to continue to allow RandomAccessSubList for configurations save with 1.4.2-. To simplify xml. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49210) Do not use ArrayList#sublist()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49210 Re: Do not use ArrayList#sublist() Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/utility/TextareaStringListUtility.java src/main/resources/META-INF/hudson.remoting.ClassFilter src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinitionJenkinsTest.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest.java src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jobs/JobWithSublist/config.xml src/test/resources/jp/ikedam/jenkins/plugins/extensible_choice_parameter/IntegrationTest/testJEP200/jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider.xml http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/afa9f3236d668a427cbcb8e504b32fc59af26dfb Log: [FIXED JENKINS-49210] JENKINS-49017 Do not use RandomAccessSubList As fix for JEP-200. Unfortunately I have to continue to allow RandomAccessSubList for configurations save with 1.4.2-. To simplify xml. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Andrew Lamonica commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 mike cirioli, yeah. That's the "workaround" mentioned most places. I was trying to set a good example to some junior employees. But, it seems that XML1.1 is just not widely supported and has even been declared "dead". I had a look at the code for this change in Jenkins and they are just hard-coding in the version number. So, we are probably pretty safe to just remedy this "hard-coded quirk" with a "hard-coded undo" in our code. Thanks for attempting to help. P.S. For people who are not attempting to do what we are doing (backing up configs), there is a JSON API that can be used in place of the XML. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title
Sam Van Oort commented on JENKINS-50199
Re: Failed pipeline jobs stuck running after incorrect resume
So, here's the things I can put together: 1. Flow completed successfully initially. Speculation: somehow there is invalid state in the list of persisted 'heads' (final FlowNodes) for the build with a null head stored, or that FlowNode wasn't persisted into storage for $reasons and cannot be loaded. 2. Because the flow ended in a way that does not evaluate as 'isComplete' or state was not persisted such that it would show as complete – this would happen if either the number of 'head' (most recent) nodes for the flow is >1 or the final 'head' FlowNode is NOT the FlowEndNode as expected (could be null) – this means the Pipeline will show as incomplete and eligible to try to resume (may be blocked if resume is disabled explicitly or fails). 3. Eventually the build is cleared from the SoftReference cache of builds... and one of the processes that iterates through builds is triggered a couple days later (there's a variety of things that can do this, but it's normal) 4. FlowNode Storage is initialized – if it can't load one of the heads OR can't load one of the startNodes (starts of a block), then it will see the null is a problem, and switch to fallback storage (to avoid overwriting original data which might be recoverable), and try to fake up a dummy set of startNodes/heads/etc. 5. This dummy storage will NOT show as complete, so it'll try to resume, sees that the build was marked "can't resume" and fails with the IOException observed. 6. This failure will invoke onProgramEnd and somehow onNewHead runs with the residual FlowNode that isn't in this storage, triggering NPE – also this triggers creation of the secondary fallbock storage ("workflow-fallback/flownodeStore.xml"). Conclusion: something must be wrong internally here, but it's not clear where precisely yet. 7. The Process from 5 triggers creation of a new FlowEndNode written to the FlowNodeStorage (observed in your workflow-fallback flowNodeStore.xml x2). But yet somehow this isn't persisted as the head for the Execution and is once again marked as incomplete and eligible to be reloaded. 8. Because the previous does not work correctly, it can happen again (seen 2x in this cycle)
Add Comment
[JIRA] (JENKINS-50228) commits count refreshing many times
Title: Message Title Paul Horvath updated an issue Jenkins / JENKINS-50228 commits count refreshing many times Change By: Paul Horvath Component/s: pipeline-stage-view-plugin Component/s: pipeline-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50228) commits count refreshing many times
Title: Message Title Paul Horvath closed an issue as Won't Fix This bug is not assigned to the correct project. That is the https://plugins.jenkins.io/pipeline-stage-view that you gave me a screenshot of Please log it to the appropriate project Jenkins / JENKINS-50228 commits count refreshing many times Change By: Paul Horvath Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-50228) commits count refreshing many times
Title: Message Title Paul Horvath assigned an issue to Unassigned Jenkins / JENKINS-50228 commits count refreshing many times Change By: Paul Horvath Assignee: Paul Horvath Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50228) commits count refreshing many times
Title: Message Title Paul Horvath updated an issue Jenkins / JENKINS-50228 commits count refreshing many times Change By: Paul Horvath Component/s: pipeline-view-plugin Component/s: pipeline-aggregator-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50228) commits count refreshing many times
Title: Message Title Paul Horvath reopened an issue Jenkins / JENKINS-50228 commits count refreshing many times Change By: Paul Horvath Resolution: Won't Fix Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16436) Build -> Prerequisites Check
Title: Message Title David Septimus updated an issue Jenkins / JENKINS-16436 Build -> Prerequisites Check Change By: David Septimus Comment: You can try the [Lockable Resources Plugin|https://wiki.jenkins.io/display/JENKINS/Lockable+Resources+Plugin] for throttling concurrent access to a specific resource. Both builds may be triggered, but only one can obtain the resource at a time and the other will be forced to wait until it is released to proceed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16436) Build -> Prerequisites Check
Title: Message Title David Septimus commented on JENKINS-16436 Re: Build -> Prerequisites Check You can try the Lockable Resources Plugin for throttling concurrent access to a specific resource. Both builds may be triggered, but only one can obtain the resource at a time and the other will be forced to wait until it is released to proceed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume 1. I didn't see any IOExceptions in the jenkins.log file. There is one is the workflow-fallback/flowNodeStore.xml file which is included in this ticket. I did get an IOException after I aborted the build with the work around. java.io.IOException: Aborting build at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:247) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:585) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:623) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:594) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:111) at jenkins.model.Jenkins._doScript(Jenkins.java:4360) at jenkins.model.Jenkins.doScript(Jenkins.java:4331) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) 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:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at
[JIRA] (JENKINS-45251) User Input text doesn't be formatted in Blue Ocean
Title: Message Title Nat Sr commented on JENKINS-45251 Re: User Input text doesn't be formatted in Blue Ocean James Dumay bump.. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50232) Resolving absolute file names: errors should show up as errors
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-50232 Resolving absolute file names: errors should show up as errors Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-16 23:12 Priority: Minor Reporter: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to
[JIRA] (JENKINS-50230) Publisher should be added arbitrary times
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50230 Publisher should be added arbitrary times Change By: Ulli Hafner Issue Type: Task New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50097) MavenConsole parser skips duplicate lines
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50097 MavenConsole parser skips duplicate lines Change By: Ulli Hafner Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50231) Tools also should define a default pattern (and a documentation)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-50231 Tools also should define a default pattern (and a documentation) Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-03-16 23:08 Priority: Minor Reporter: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-50230) Publisher should be added arbitrary times
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-50230 Publisher should be added arbitrary times Issue Type: Task Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-16 23:05 Priority: Minor Reporter: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title mike cirioli commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Assuming you don't need to support special characters (like control characters) you could just change the xml declartion to be v1.0 and then process the file with whatever tools you currently use. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Ahh, nevermind, I missed that in the listing. That confirms another part of the theory. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Mike Kozell Also, do you see anything anything in a directory "workflow-fallback" (perhaps with a flowNodeStore.xml)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Thanks Mike Kozell that data is indeed very useful and solidly confirms my working theory (which I will explain in a moment). Before I explain (since it'll take a bit to write up and I'm hoping you're still around), please could you do one more analysis: 1. Do you see any IOExceptions in the jenkins log or build log for these builds 2. Please can you do a search for "FlowStartNode" and "FlowEndNode" in both flowNodeStore.xml files and report the id and any error shown for that element? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22367) Move JDKInstaller to a plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22367 Re: Move JDKInstaller to a plugin Code changed in jenkins User: Devin Nusbaum Path: core/src/main/java/hudson/model/JDK.java core/src/main/java/hudson/tools/JDKInstaller.java core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK.jelly core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_bg.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_de.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_es.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_it.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_ja.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_pt_BR.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_sr.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK_zh_TW.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential.jelly core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_bg.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_de.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_es.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_it.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_ja.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_pt_BR.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_sr.properties core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential_zh_TW.properties core/src/main/resources/hudson/tools/JDKInstaller/config.jelly core/src/main/resources/hudson/tools/JDKInstaller/config_bg.properties core/src/main/resources/hudson/tools/JDKInstaller/config_ca.properties core/src/main/resources/hudson/tools/JDKInstaller/config_da.properties core/src/main/resources/hudson/tools/JDKInstaller/config_de.properties core/src/main/resources/hudson/tools/JDKInstaller/config_en_GB.properties core/src/main/resources/hudson/tools/JDKInstaller/config_es.properties core/src/main/resources/hudson/tools/JDKInstaller/config_fi.properties core/src/main/resources/hudson/tools/JDKInstaller/config_fr.properties core/src/main/resources/hudson/tools/JDKInstaller/config_he.properties core/src/main/resources/hudson/tools/JDKInstaller/config_it.properties core/src/main/resources/hudson/tools/JDKInstaller/config_ja.properties core/src/main/resources/hudson/tools/JDKInstaller/config_lt.properties core/src/main/resources/hudson/tools/JDKInstaller/config_lv.properties core/src/main/resources/hudson/tools/JDKInstaller/config_nl.properties core/src/main/resources/hudson/tools/JDKInstaller/config_pl.properties core/src/main/resources/hudson/tools/JDKInstaller/config_pt_BR.properties core/src/main/resources/hudson/tools/JDKInstaller/config_pt_PT.properties core/src/main/resources/hudson/tools/JDKInstaller/config_ru.properties core/src/main/resources/hudson/tools/JDKInstaller/config_sk.properties core/src/main/resources/hudson/tools/JDKInstaller/config_sr.properties core/src/main/resources/hudson/tools/JDKInstaller/config_sv_SE.properties core/src/main/resources/hudson/tools/JDKInstaller/config_zh_CN.properties
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Mike Kozell Attachment: workflow-fallback-flowNodeStore.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Mike Kozell Attachment: flowNodeStore.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Mike Kozell Attachment: build.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Mike Kozell Attachment: build.log Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy updated JENKINS-49852 Jenkins / JENKINS-49852 Collect Pipeline usage telemetry Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy updated JENKINS-49852 Jenkins / JENKINS-49852 Collect Pipeline usage telemetry Change By: R. Tyler Croy Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy stopped work on JENKINS-49852 Change By: R. Tyler Croy Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title R. Tyler Croy resolved as Fixed Since the error telemetry will cover things for now, I'm going to go ahead and close this. Jenkins / JENKINS-49892 Evaluate options for collecting "method instrumentation" telemetry Change By: R. Tyler Croy Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-49861) Disable master executors by default
Title: Message Title R. Tyler Croy updated JENKINS-49861 Since I merged this PR for ya, I'll close this while I'm looking at the board Jenkins / JENKINS-49861 Disable master executors by default Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title John Jones commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile PR created here: https://github.com/jenkinsci/ssh-credentials-plugin/pull/33 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49869) Disable non-Pipeline/Folder items in the new item view
Title: Message Title R. Tyler Croy commented on JENKINS-49869 Re: Disable non-Pipeline/Folder items in the new item view Daniel pointed this out: https://github.com/daniel-beck/hide-maven-plugin/ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50229) API for cucumber-reports is outdated
Title: Message Title Damian Szczepanik created an issue Jenkins / JENKINS-50229 API for cucumber-reports is outdated Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-03-16 21:18 Priority: Minor Reporter: Damian Szczepanik I found that https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.helpers.publisher.PublisherContext.cucumberReports provides API which is not valid any more. I would like to provide/update the API but I'm not sure how. Can you give my a hint or PR for similar problem? Add Comment
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Andrew Lamonica commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Does anyone have a good recommendation for an XML 1.1 Parser. We are a .NET-shop. But, Microsoft's standard XML parsers don't support XML 1.1. Looking around the internet, I see a lot of "workarounds", but not any parsers that actually support version 1.1. My application is not performance-critical, so anything that converts XML 1.1 into another supported language (JSON, XML 1.0, YAML, protobuf, etc) would be fine. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49216) Implement way to disable Bitbucket build status updates
Title: Message Title benoit guerin closed an issue as Fixed Jenkins / JENKINS-49216 Implement way to disable Bitbucket build status updates Change By: benoit guerin Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49866) Automatically configure Docker Cloud if the docker.sock is available
Title: Message Title R. Tyler Croy commented on JENKINS-49866 Re: Automatically configure Docker Cloud if the docker.sock is available Baptiste Mathus, sorry for the vagueness of the ticket. As far as I am concerned the "acceptance criteria" would be that if /var/run/docker.sock is available to Jenkins, that the Docker plugin is automatically configured in order to allow a user to run a "normal" Pipeline now that JENKINS-49861 has been implemented. If this is something we need a custom plugin to accomplish then I'd like to see some research proving that to be necessary. My hunch is that it would likely be easier for us to leverage existing plugins and then add some smarts into the jenkins/evergreen container to generate the appropriate Configuration as Code. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50207) Transient error "container [*] does not exist in pod"
Title: Message Title
Michael Maletich updated an issue
Jenkins / JENKINS-50207
Transient error "container [*] does not exist in pod"
Change By:
Michael Maletich
About 1 in every 4 of our builds dies with the error "container [] does not exist in pod []". Rerunning the build usually fixes the error. example strack trace:{noformat}java.io.IOException: container [docker] does not exist in pod [jenkins-slave-bn834-q2pw4] at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:307) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:136) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:132) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:186) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:66) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:176) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:133) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:30) at ___cps.transform___(Native Method) at
[JIRA] (JENKINS-50228) commits count refreshing many times
Title: Message Title akostadinov created an issue Jenkins / JENKINS-50228 commits count refreshing many times Issue Type: Bug Assignee: Paul Horvath Attachments: strange_updates.png Components: pipeline-aggregator-view-plugin Created: 2018-03-16 20:44 Priority: Minor Reporter: akostadinov Hi, when a build is in progress and I stay at "stage view" watching progress of the pipeline, I see that the commit count for the archived builds is constantly refreshing. Each time progress moves for the running pipeline, all archived builds do refresh their commit counts. Sounds like a great idea to remove this. Attaching a screenshot from Firefox 58. Add Comment
[JIRA] (JENKINS-50195) Create a non root user for running Jenkins and the evergreen-client
Title: Message Title R. Tyler Croy commented on JENKINS-50195 Re: Create a non root user for running Jenkins and the evergreen-client I don't have a good notion right now of whether supervisord needs root or not. I'm going to leave this ticket in the backlog, but feel free to pick it up for Milestone 1 if the other stuff gets tackled in good time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50227) Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50227 Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded Change By: Karl Shultz Attachment: har-file.har Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50227) Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded
Title: Message Title Karl Shultz commented on JENKINS-50227 Re: Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded A very minimal .har file is now attached from recreating the problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50227) Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50227 Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded Issue Type: Bug Assignee: Unassigned Attachments: image-2018-03-16-15-57-47-154.png, image-2018-03-16-16-04-29-843.png Components: blueocean-pipeline-editor-plugin Created: 2018-03-16 20:09 Environment: Jenkins: Core 2.11 Blue Ocean 1.5.0-beta-2 All plugins at experimental update center levels Running on Ubuntu Client: Fedora Workstation 27 Google Chrome 65.0.3325.162 Priority: Major Reporter: Karl Shultz Summary: When editing a Pipeline with the Blue Ocean Pipeline Editor, clicking the rightmost ( + ) node to add a new stage, and then clicking the ( + ) node below it, produces a Discovered while working on ATH tests. Steps to recreate: 1. Edit an existing Pipeline. 2. Open your browser's console and switch to the Network tab. 3. Click the rightmost ( + ) button to add a new stage: 4. Click on the ( + ) node directly below, without having done anything else: 5. Notice the error being displayed in the console: blueocean.js:58235 Unhandled Error: "RangeError: Maximum call stack size exceeded\nat EditorMain.createStage (http://172.18.40.95:8080/adjuncts/f5dd3f98/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:68174:36)\nat EditorMain.createStage
[JIRA] (JENKINS-50227) Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50227 Add stage to unnamed parallel wrapper stage: console shows Maximum call stack size exceeded Issue Type: Bug Assignee: Unassigned Attachments: image-2018-03-16-15-57-47-154.png, image-2018-03-16-16-04-29-843.png Components: blueocean-pipeline-editor-plugin Created: 2018-03-16 20:09 Environment: Jenkins: Core 2.11 Blue Ocean 1.5.0-beta-2 All plugins at experimental update center levels Running on Ubuntu Client: Fedora Workstation 27 Google Chrome 65.0.3325.162 Priority: Major Reporter: Karl Shultz Summary: When editing a Pipeline with the Blue Ocean Pipeline Editor, clicking the rightmost ( + ) node to add a new stage, and then clicking the ( + ) node below it, produces a Discovered while working on ATH tests. Steps to recreate: 1. Edit an existing Pipeline. 2. Open your browser's console and switch to the Network tab. 3. Click the rightmost ( + ) button to add a new stage: 4. Click on the ( + ) node directly below, without having done anything else: 5. Notice the error being displayed in the console: blueocean.js:58235 Unhandled Error: "RangeError: Maximum call stack size exceeded\nat EditorMain.createStage (http://172.18.40.95:8080/adjuncts/f5dd3f98/org/jenkins/ui/jsmodules/blueocean-pipeline-editor/jenkins-js-extension.js:68174:36)\nat EditorMain.createStage
[JIRA] (JENKINS-50171) LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Title: Message Title Andrew Bayer commented on JENKINS-50171 Re: LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start Yeah, switching to getSimpleName() seems to be the right answer, so PR up at https://github.com/jenkinsci/workflow-cps-plugin/pull/214 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50171) LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Title: Message Title Andrew Bayer updated JENKINS-50171 Jenkins / JENKINS-50171 LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50174) pipeline job status page cannot be rendered properly if a build hits JENKINS-50171
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50174 pipeline job status page cannot be rendered properly if a build hits JENKINS-50171 Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50174) pipeline job status page cannot be rendered properly if a build hits JENKINS-50171
Title: Message Title Andrew Bayer commented on JENKINS-50174 Re: pipeline job status page cannot be rendered properly if a build hits JENKINS-50171 I pretty strongly feel that this is just a symptom of JENKINS-50171, not a separate issue, but I'll let you persuade me otherwise before I close it as a dupe. =) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50171) LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Title: Message Title Andrew Bayer started work on JENKINS-50171 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50171) LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-50171 LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50172) load step doesn't generate unique name for classes
Title: Message Title Andrew Bayer resolved as Duplicate ...actually, gonna use JENKINS-50171 for this since they're entirely the same issue. Jenkins / JENKINS-50172 load step doesn't generate unique name for classes Change By: Andrew Bayer Status: In Progress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-50171) LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Title: Message Title
Andrew Bayer commented on JENKINS-50171
Re: LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Comment copied over from JENKINS-50172: The problem appears to stem from the fact that load will actually give everything an autogenerated class name (i.e., Script1, Script2, etc). This is because load doesn't actually parse/compile the file passed to it directly - it reads that file (so, in this case, src/org/foo/devops/Utility.groovy), and parses it directly, autogenerating the class name. But when there's a package, things get...confused. The resulting loadedScripts key in CpsFlowExecution ends up as org.foo.devops.Script1, rather than Script1. Which is fine? I guess? Well, until we try to resume. Then, when we get to CpsFlowExecution#parseScript(), we end up trying to CpsGroovyShell#parse(new GroovyCodeSource("code from Utility.groovy", "org.foo.devops.Script1", DEFAULT_CODE_BASE)), and that confuses Groovy's parsing logic: if you tell it "here's a class name including package to parse, and here's the text to parse", it's going to get very confused when there's no class Script1 inside that text. So it ends up deciding the fully qualified class name is "(package).(package but with periods replaced by underscores)" for...reasons? And that results in duplicate class names and everything blows up. So for the moment? Don't put package ... in Groovy files you're going to load. It will break things. Obviously. I think the fix for this is to just put getClass().getSimpleName() in as the key in CpsFlowExecution#loadedScripts rather than the current getClass().getName() - this definitely fixes this problem but I'm a bit wary as to whether there could be side effects. And regardless of that fix, I would not be at all surprised if there were other weird edge cases around load and packages, so...just don't do that.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50172) load step doesn't generate unique name for classes
Title: Message Title Andrew Bayer started work on JENKINS-50172 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50172) load step doesn't generate unique name for classes
Title: Message Title
Andrew Bayer commented on JENKINS-50172
Re: load step doesn't generate unique name for classes
The problem appears to stem from the fact that load will actually give everything an autogenerated class name (i.e., Script1, Script2, etc). This is because load doesn't actually parse/compile the file passed to it directly - it reads that file (so, in this case, src/org/foo/devops/Utility.groovy), and parses it directly, autogenerating the class name. But when there's a package, things get...confused. The resulting loadedScripts key in CpsFlowExecution ends up as org.foo.devops.Script1, rather than Script1. Which is fine? I guess? Well, until we try to resume. Then, when we get to CpsFlowExecution#parseScript(), we end up trying to CpsGroovyShell#parse(new GroovyCodeSource("code from Utility.groovy", "org.foo.devops.Script1", DEFAULT_CODE_BASE)), and that confuses Groovy's parsing logic: if you tell it "here's a class name including package to parse, and here's the text to parse", it's going to get very confused when there's no class Script1 inside that text. So it ends up deciding the fully qualified class name is "(package).(package but with periods replaced by underscores)" for...reasons? And that results in duplicate class names and everything blows up. So for the moment? Don't put package ... in Groovy files you're going to load. It will break things. Obviously. I think the fix for this is to just put getClass().getSimpleName() in as the key in CpsFlowExecution#loadedScripts rather than the current getClass().getName() - this definitely fixes this problem but I'm a bit wary as to whether there could be side effects. And regardless of that fix, I would not be at all surprised if there were other weird edge cases around load and packages, so...just don't do that.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50172) load step doesn't generate unique name for classes
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50172 load step doesn't generate unique name for classes Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50172) load step doesn't generate unique name for classes
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-50172 load step doesn't generate unique name for classes Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Harsimrat Khattra commented on JENKINS-49033 Re: Issue with HPE Application Automation Tools plugin Hi Yafim Kazak, any updates on this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50226) Uft integration - after changing Octane configuration to another octane in Jenkins - test results are still sent to previously configured Octane
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-50226 Uft integration - after changing Octane configuration to another octane in Jenkins - test results are still sent to previously configured Octane Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-03-16 19:29 Labels: octane uft-integration 5.3.4-beta Priority: Major Reporter: Michael Seldin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Stephen Connolly commented on JENKINS-47496 Re: No automatic builds for tags You could have a build storm if you have 200 tags, they all get discovered and queued for building... and your tags are set up to deploy to production because they are tags... and jenkins does not guarantee the order in which the tags will be discovered or actually executed... so production is constantly cycling different versions. In any case, if you want to build tags just install the Basic Branch Build Strategies plugin and configure it: https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc#tags Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Stephen Connolly commented on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up The original design of the API was that pull requests would be handled as a separate source in the same multibranch... similarly you can add forks of the same repo... now in retrospect it one could argue that it was a bad design decision to do it that way in 2013... but there are users who use the multiple sources, so we cannot remove it... which means a branch being deleted in one source does not mean the branch job should be deleted. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50225) Blue Ocean null pointer exception opening a matrix project
Title: Message Title Mark Waite resolved as Won't Fix Jenkins / JENKINS-50225 Blue Ocean null pointer exception opening a matrix project Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50225) Blue Ocean null pointer exception opening a matrix project
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-50225
Blue Ocean null pointer exception opening a matrix project
Change By:
Mark Waite
Matrix projects are not supported by Blue Ocean. Previously, when a user mistakenly attempted to open a matrix project, it opened with a warning.With the 1.4.2 releases of the Blue Ocean plugins, it now reports a null pointer exception and does not render the page correctly. The exception is:{noformat}WARNING: Failed to get "pipelineFolderNames" from a io.jenkins.blueocean.rest.impl.pipeline.MatrixProjectImpljava.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:167) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Export.writeOne(Export.java:148) at io.jenkins.blueocean.commons.stapler.Export.serveExposedBean(Export.java:136) at io.jenkins.blueocean.commons.stapler.Export.doJson(Export.java:79) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:70) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:136) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:119) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) 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:841) at
[JIRA] (JENKINS-49314) Allow configurable readTimeout for jira-steps-plugin
Title: Message Title Naresh Rayapati commented on JENKINS-49314 Re: Allow configurable readTimeout for jira-steps-plugin Merged above pull request, will release artifact soon once after a bit of local testing. Thanks a bunch for your contribution Chris White. Resolving this JIRA for now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49314) Allow configurable readTimeout for jira-steps-plugin
Title: Message Title Naresh Rayapati updated JENKINS-49314 Jenkins / JENKINS-49314 Allow configurable readTimeout for jira-steps-plugin Change By: Naresh Rayapati Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50026) Hubot Steps 2.0.0 Enhancements List
Title: Message Title Naresh Rayapati started work on JENKINS-50026 Change By: Naresh Rayapati Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49314) Allow configurable readTimeout for jira-steps-plugin
Title: Message Title Naresh Rayapati commented on JENKINS-49314 Re: Allow configurable readTimeout for jira-steps-plugin Have open up a new pull request with comments being addressed: https://github.com/jenkinsci/jira-steps-plugin/pull/67 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50225) Blue Ocean null pointer exception opening a matrix project
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-50225 Blue Ocean null pointer exception opening a matrix project Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-03-16 18:44 Environment: Jenkins 2.107.1 as recorded in my [docker-lfs repo|https://github.com/MarkEWaite/docker-lfs/blob/2c899abe75a3425ac1621f02a7701fa53b80a418/Dockerfile-slim] Priority: Trivial Reporter: Mark Waite Matrix projects are not supported by Blue Ocean. Previously, when a user mistakenly attempted to open a matrix project, it opened with a warning. With the 1.4.2 releases of the Blue Ocean plugins, it now reports a null pointer exception and does not render the page correctly. The exception is: WARNING: Failed to get "pipelineFolderNames" from a io.jenkins.blueocean.rest.impl.pipeline.MatrixProjectImpl java.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:167) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199)
[JIRA] (JENKINS-50224) Pipeline stage view not displaying Stages
Title: Message Title Drew Kulick updated an issue Jenkins / JENKINS-50224 Pipeline stage view not displaying Stages Change By: Drew Kulick I am seeing the following stack trace when rendering the pipeline stage view. The grid for the view never shows up (obviously) java ava .lang.NullPointerException at com.cloudbees.workflow.rest.external.AtomFlowNodeExt.addParentNodeRefs(AtomFlowNodeExt.java:84) at com.cloudbees.workflow.rest.external.AtomFlowNodeExt.create(AtomFlowNodeExt.java:76) at com.cloudbees.workflow.rest.external.ChunkVisitor.makeAtomNode(ChunkVisitor.java:68) at com.cloudbees.workflow.rest.external.ChunkVisitor.atomNode(ChunkVisitor.java:154) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.fireVisitChunkCallbacks(ForkScanner.java:751) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:769) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:633) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:321) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:309) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:69) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30)Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at
[JIRA] (JENKINS-50224) Pipeline stage view not displaying Stages
Title: Message Title Drew Kulick updated an issue Jenkins / JENKINS-50224 Pipeline stage view not displaying Stages Change By: Drew Kulick I am seeing the following stack trace when rendering the pipeline stage view. The grid for the view never shows up (obviously) ava java .lang.NullPointerException at com.cloudbees.workflow.rest.external.AtomFlowNodeExt.addParentNodeRefs(AtomFlowNodeExt.java:84) at com.cloudbees.workflow.rest.external.AtomFlowNodeExt.create(AtomFlowNodeExt.java:76) at com.cloudbees.workflow.rest.external.ChunkVisitor.makeAtomNode(ChunkVisitor.java:68) at com.cloudbees.workflow.rest.external.ChunkVisitor.atomNode(ChunkVisitor.java:154) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.fireVisitChunkCallbacks(ForkScanner.java:751) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:769) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:633) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:321) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:309) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:69) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30)Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Kevin Lannen commented on JENKINS-43820 Re: Stage name must be a string literal This is a serious blocker to using the declarative syntax to define a pipeline in a shared library. What is the "conscious design decision" that led to this? From my perspective there is no downside to allowing this flexibility. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50224) Pipeline stage view not displaying Stages
Title: Message Title Drew Kulick created an issue Jenkins / JENKINS-50224 Pipeline stage view not displaying Stages Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-03-16 18:27 Environment: Jenkins 2.111 Priority: Minor Reporter: Drew Kulick I am seeing the following stack trace when rendering the pipeline stage view. The grid for the view never shows up (obviously) java.lang.NullPointerException Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30) Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at
[JIRA] (JENKINS-50171) LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Title: Message Title Andrew Bayer commented on JENKINS-50171 Re: LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start I'd say this is just a symptom of JENKINS-50172. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title Mike Kozell created an issue Jenkins / JENKINS-50223 Pipeline Jenkins master ran out of Java Metaspace Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-03-16 18:03 Priority: Major Reporter: Mike Kozell Setup Jenkins v2.89.3 / v2.89.4 LTS Pipeline API Plugin: 2.26 Pipeline Nodes and Processes Plugin: 2.19 Durable Task Plugin: 1.18 Pipeline Job Plugin: 2.17 Pipeline Shared Groovy Libraries Plugin: 2.9 Pipeline Supporting APIs Plugin: 2.18 Pipeline Groovy Plugin: 2.45 Script Security Plugin: 1.41 Pipeline Default Speed/Durability Level: Performance-Optimized "Do not allow the pipeline to resume if the master restarts": Enabled on all jobs Problem Shortly after upgrading from Jenkins 2.60.3 to Jenkins 2.89.3 LTS, we experienced a java.lang.OutOfMemoryError: Metaspace error. I'm unsure if this a bug or if increased Java Metaspace is to be expected in the newer version of Jenkins and pipeline plugins. Details Jenkins v2.60.3 In Jenkins 2.60.3 we used the memory parameters below and the Java nonheap space (Metaspace) stayed between 350mb and 550mb. We ran for months without restarting Jenkins. -XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:+ParallelRefProcEnabled -XX:+UseStringDeduplication -XX:MaxMetaspaceSize=1g -XX:MetaspaceSize=256M -Xms4g -Xmx8g -Dgroovy.use.classvalue=true Jenkins v2.89.3 After upgrading to Jenkins 2.89.3 and upgrading all of the plugins, we used the Java memory settings below. We removed the "groovy.use.classvalue=true" parameter based on the recommendation here: https://support.cloudbees.com/hc/en-us/articles/115001505172-Jenkins-hangs-due-to-Groovy-ClassInfo-deadlock. We saw the Java nonheap memory fluctuate between 250mb and 750mb slowing trending upwards. After a few weeks, nonheap memory was at 1GB and Jenkins no longer responded to requests. The log file was full of java.lang.OutOfMemoryError: Metaspace errors. -XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:+ParallelRefProcEnabled
[JIRA] (JENKINS-50119) Dynamic DSL for workflowMultiBranchProjectFactory not working
Title: Message Title Steven Foster commented on JENKINS-50119 Re: Dynamic DSL for workflowMultiBranchProjectFactory not working Nevermind that, I checked out 1.68 instead and the same changes worked fine. I guess recent work on master has temporarily broken multibranchPipelineJobs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Mark Waite commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Thanks Bill Hamilton! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Bill Hamilton commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Mark WaiteStephen Connolly Guys, I just want to confirm the use cases that should be tested around this: Both the @Library directive, and the library() DSL step, should insure that specifying branches, PRs, tags, and hashes all work Thanks, -Bill Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50119) Dynamic DSL for workflowMultiBranchProjectFactory not working
Title: Message Title Steven Foster commented on JENKINS-50119 Re: Dynamic DSL for workflowMultiBranchProjectFactory not working I think the issue is multibranchPipelineJob should be using workflowBranchProjectFactory rather than workflowMultiBranchProject factory. I tried to implement it in monkey-see monkey-do fashion by creating a BranchProjectFactory context based on MultiBranchProjectFactoryContext, changing all references to MultiBranchProjectFactory to BranchProjectFactory, updating MultibranchWorkflowJob to use BranchProjectFactory, and updating a test. It's a bit over my head though and I'm hitting issues testing it out. It shows in the api viewer (which 404s in ./gradlew server) but if I try to make any kind of multibranchPipelineJob I get groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method groovy.util.XmlParser#parse. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.io.File] [class java.io.InputStream] [class java.io.Reader] [class java.lang.String] [class org.xml.sax.InputSource] at groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3263) at groovy.lang.MetaClassImpl.chooseMethodInternal(MetaClassImpl.java:3216) at groovy.lang.MetaClassImpl.chooseMethod(MetaClassImpl.java:3159) at groovy.lang.MetaClassImpl.getMethodWithCachingInternal(MetaClassImpl.java:1331) at groovy.lang.MetaClassImpl.createPojoCallSite(MetaClassImpl.java:3391) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(CallSiteArray.java:132) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(CallSiteArray.java:166) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at javaposse.jobdsl.dsl.Folder.getNodeTemplate(Folder.groovy:110) 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 org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.MethodMetaProperty$GetBeanMethodMetaProperty.getProperty(MethodMetaProperty.java:76) at org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.callGroovyObjectGetProperty(GetEffectivePogoPropertySite.java:68) at javaposse.jobdsl.dsl.Item.getNode(Item.groovy:45) 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 org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.MethodMetaProperty$GetBeanMethodMetaProperty.getProperty(MethodMetaProperty.java:76) at org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.callGroovyObjectGetProperty(GetEffectivePogoPropertySite.java:68) at javaposse.jobdsl.dsl.Item.getXml(Item.groovy:34) at
[JIRA] (JENKINS-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Andrew Bayer commented on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled fwiw, I think this likely only will happen with a flyweight task - so you could probably brew up a reproduction case with a matrix job, but I doubt you could do so with a freestyle job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title Baptiste Mathus commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system FTR, meeting added in the repo as we'll do for all of them in the future: https://github.com/jenkins-infra/evergreen/tree/master/docs/meetings/2018-03-18-JENKINS-49406-quality-bar Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Andrew Bayer commented on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled So Queue#maintain() is running twice, one immediately after the other, in some cases - probably race conditiony, not yet sure how the two are getting called. Anyway, the first run is making the first item in the queue buildable and calls makeBuildable on the item, removing said item from blockedProjects, and, via makeFlyweightTaskBuildable and createFlyWeightTaskRunnable, starting the flyweight task and adding the first item to pendings. All is well and good. But then the next run of maintain starts - and it can't find the task for the item we just started (theoretically) and put in pendings on any executor...so it removes the item from pendings. Then it gets to checking the queue again, and the new first item doesn't have anything blocking it (i.e., nothing in buildables or pending) and so...it goes through the same process as the previous item did in the previous maintain run. End result: two builds get started at the same time. So - definitely a race condition. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37500) scm-syn-configuration issues with multi branch project
Title: Message Title Ethan Spoelstra commented on JENKINS-37500 Re: scm-syn-configuration issues with multi branch project I can confirm the hpi built by James Hogarth resolved this issue on one of our instances where we had been testing a multibranch job configuration via Bitbucket source. https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/49#issuecomment-273456696 The change has been merged, there just needs to be a release with the new functionality. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Ernst de Haan Perhaps someone (you or someone else) can implement such a “hack” as a plugin – probably with a fat disclaimer indicating that many of the scenarios (as mentioned by Sam Van Oort) are not covered I was actually going to suggest that. Some of those experiments can provide new ideas for how to implement a comprehensive feature – and if they work really well they may even be requested to directly merge into the core of Pipeline. More often they provide inspiration that leads one of us to hack out the ultimate solution. Personally, I absolutely hate that we can't easily address this improvement, but past lessons have also taught us that a maintainable and robust solution is much better for this kind of challenge than a quick-and-dirty solution that opens up problems down the road. Maybe someone will be able to come up with a solution that does not impose those risks though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Ruben Perez It is a high priority to address this and in my personal upcoming work, but right now the highest priority is ensuring Pipeline does not cause system stability problems. As far as the architecture: I took the time to write up a detailed explanation of the situation in hopes it might lead to something productive (maybe even a PR), and it really is not constructive to simply say "your architecture is wrong." While you're entitled to your opinion, let me ask you this: how would you feel if you were putting many of your nights and weekends into improving something and someone said that to you? This is an open source project and we only have so many engineers no matter how hard we work – if you think you could improve upon the architecture you're more than welcome to submit PRs that accomplish this goal. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy started work on JENKINS-49852 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47789) Git BuildData entry leaks in from Gerrit event triggered builds in build.xml
Title: Message Title Jacob Keller commented on JENKINS-47789 Re: Git BuildData entry leaks in from Gerrit event triggered builds in build.xml This is a duplicate of 19022, though Gerrit makes this significantly worse. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Ernst de Haan commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Kevin Phillips Perhaps someone (you or someone else) can implement such a “hack” as a plugin – probably with a fat disclaimer indicating that many of the scenarios (as mentioned by Sam Van Oort) are not covered. That would at least reduce the pain a bit, and it would “buy some time” to get the real solution in place. Sam Van Oort: Your suggestion to […] simply not display an UNSTABLE status at the UI level in any situation […] may be of help to some people, for whom it may make sense to support that with an configuration flag somewhere. But for many (including myself) this would not add much value, if any. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49806) Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49806 Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials Discussed some thoughts on pre-release security verifications we might be able to enforce for plugins considered "essential" with Daniel Beck today. Including a minimum quality bar for essential plugins should definitely be a key criteria 23:54 @ we already have some automation for that -- InjectedTest takes care of XSS on recent baselines, configRoundTrip takes care of password fields used for plain text values. The problem is these are opt in (the latter) and often opted out (the former). 00:03 @ rtyler perhaps -- I got started with https://github.com/jenkins-infra/jenkins.io/blame/master/content/doc/developer/plugin-development/build-process.adoc#L29 but including it in content would have required too much yak shaving Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Ruben Perez commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Then your architecture is wrong. It cannot support something fundamentally needed. The sooner you change it, the better. This project goes nowhere without this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-49632 Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Change By: Cyrille Le Clerc Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc resolved as Fixed Jenkins / JENKINS-49632 Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Change By: Cyrille Le Clerc Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Kevin Phillips Believe me, we know exactly how irritating these limitations of the Pipeline architecture are because we "drink our own champagne" internally and use test result reporting extensively in Jenkins Pipelines. The problem is that this is directly tied to the limitations of the Pipeline data model, which internally is pass/fail – everything else is computed in a logical way on the basis of ErrorActions, Input Actions, whether or not the FlowNode in question is the tip of a incomplete build (In-progress). Anything that modifies how we store status is unfortunately a permanent change because it would have to work by recording data in the model, either by Actions on FlowNodes, or by some internal state, or both. Thus any "hacks" we added would be a part of Pipeline forever – we could ignore the extra data but it would introduce compatibility issues. The extra level of complexity is that any behavior needs to be consistent across (potentially nested) parallels, nested blocks, and has to have something like a try/catch construct to let users override results – which has to behave logically in the face of a full & potentially complex graph structure. Take a look at Pipeline Graph Analysis plugin and you'll see what I mean about the complexity (also the APIs for working with the graph in https://github.com/jenkinsci/workflow-api-plugin/tree/master/src/main/java/org/jenkinsci/plugins/workflow/graphanalysis). The simple fix would be to simply not display an UNSTABLE status at the UI level in any situation for Pipelines, only at the overall build level. Would that be preferred? Because that's a change we can do without too much extra hassle. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
