[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException yeah thats the one I sent to and also tried to subscribe like it mentioned. Both failed telling me the group does not exist. Now I guess I have to try gitter Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException Mark Waite ok this is not easy. I've tried contacting both the users and dev email addresses on the Jenkins users mailing list and both just get returned emails saying the group does not exist. What is the jenkins support mailing list? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException ok I will try that. This was a new bug I filed this morning so I don't know how it got merged onto this one. I created a new issue. It is breaking or production stack with over 700 jobs and over 400 users Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title
Gregor Philp commented on JENKINS-47660
Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
This is not to do with a large repository or timeout. The repo is extremely small I am testing with and the job fails in just over 20 seconds. I remove that plugin and the job works fine. timestamps { node ('ECS-CO7-LATEST') { stage ('Checkout') { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: '***, url: 'g...@github.move.com:IT-Operations/aws-certificates.git']]]) } stage ('sleep') { sh ''' sleep 20 ''' } stage ('Clean') { cleanWs() } } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException ERROR we get after upgrading these plugins and trying to checkout in a pipeline job 17:52:07 Cloning the remote Git repository 17:52:07 ERROR: Error cloning remote repo 'origin' 17:52:07 hudson.plugins.git.GitException: java.io.IOException: Remote call on JNLP4-connect connection from ip-10-192-23-154.us-west-2.compute.internal/10.192.23.154:23354 failed 17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:169) 17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 17:52:07 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 17:52:07 at java.lang.reflect.Method.invoke(Method.java:498) 17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) 17:52:07 at com.sun.proxy.$Proxy140.execute(Unknown Source) 17:52:07 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146) 17:52:07 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186) 17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) 17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) 17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) 17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) 17:52:07 at hudson.security.ACL.impersonate(ACL.java:290) 17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) 17:52:07 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 17:52:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 17:52:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 17:52:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 17:52:07 at java.lang.Thread.run(Thread.java:748) 17:52:07 Caused by: java.io.IOException: Remote call on JNLP4-connect connection from ip-10-192-23-154.us-west-2.compute.internal/10.192.23.154:23354 failed 17:52:07 at hudson.remoting.Channel.call(Channel.java:961) 17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) 17:52:07 ... 19 more 17:52:07 Caused by: java.lang.IllegalAccessError: tried to access field hudson.remoting.Channel.executor from class org.jenkinsci.remoting.util.AnonymousClassWarnings 17:52:07 at org.jenkinsci.remoting.util.AnonymousClassWarnings.check(AnonymousClassWarnings.java:65) 17:52:07 at org.jenkinsci.remoting.util.AnonymousClassWarnings$1.annotateClass(AnonymousClassWarnings.java:121) 17:52:07 at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1290) 17:52:07 at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1231) 17:52:07 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1427) 17:52:07 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) 17:52:07 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) 17:52:07 at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:185) 17:52:07 at hudson.console.ConsoleNote.encode(ConsoleNote.java:211) 17:52:07 at hudson.plugins.timestamper.TimestampNotesOutputStream.eol(TimestampNotesOutputStream.java:70) 17:52:07 at
[JIRA] (JENKINS-55455) after upgrading plugins for pipeline: Declarative, pipeline jobs cannot checkout from GHE
Title: Message Title Gregor Philp created an issue Jenkins / JENKINS-55455 after upgrading plugins for pipeline: Declarative, pipeline jobs cannot checkout from GHE Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-01-08 19:23 Environment: Jenkins 2.150.1 Plugins we have current version of Pipeline: Declarative v1.3.2 (trying to upgrade to 1.3.4) Pipeline: Declarative Extension Points API v1.3.2 (trying to upgrade to 1..3.4) Pipeline: Model API v1.3.2 (trying to upgrade to 1.3.4) Priority: Major Reporter: Gregor Philp Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55281) Error viewing build log
Title: Message Title Gregor Philp commented on JENKINS-55281 Re: Error viewing build log here's the whole stack trace, running jenkins 2.150.1 Stack trace java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:270) at hudson.plugins.ansicolor.ColorConsoleAnnotator$1EmitterImpl.emitHtml(ColorConsoleAnnotator.java:74) at hudson.plugins.ansicolor.AnsiAttributeElement.emitClose(AnsiAttributeElement.java:42) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.closeTagOfType(AnsiHtmlOutputStream.java:150) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.setForegroundColor(AnsiHtmlOutputStream.java:335) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.processDefaultTextColor(AnsiHtmlOutputStream.java:589) at hudson.plugins.ansicolor.AnsiOutputStream.processEscapeCommand(AnsiOutputStream.java:352) at hudson.plugins.ansicolor.AnsiOutputStream.write(AnsiOutputStream.java:138) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.write(AnsiHtmlOutputStream.java:220) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:55) at hudson.plugins.ansicolor.ColorConsoleAnnotator.annotate(ColorConsoleAnnotator.java:91) at hudson.console.ConsoleAnnotator$ConsoleAnnotatorAggregator.annotate(ConsoleAnnotator.java:108) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:148) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1$1.write(FileLogStorage.java:238) at java.io.FilterOutputStream.write(FilterOutputStream.java:125) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:90) at org.kohsuke.stapler.framework.io.LargeText$HeadMark.moveTo(LargeText.java:314) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:229) at hudson.console.AnnotatedLargeText.writeRawLogTo(AnnotatedLargeText.java:163) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203) at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:144) at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:264) at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:92) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at
[JIRA] (JENKINS-55281) Error viewing build log
Title: Message Title Gregor Philp commented on JENKINS-55281 Re: Error viewing build log here's the whole stack trace, running jenkins 2.150.1 Stack trace java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:270) at hudson.plugins.ansicolor.ColorConsoleAnnotator$1EmitterImpl.emitHtml(ColorConsoleAnnotator.java:74) at hudson.plugins.ansicolor.AnsiAttributeElement.emitClose(AnsiAttributeElement.java:42) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.closeTagOfType(AnsiHtmlOutputStream.java:150) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.setForegroundColor(AnsiHtmlOutputStream.java:335) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.processDefaultTextColor(AnsiHtmlOutputStream.java:589) at hudson.plugins.ansicolor.AnsiOutputStream.processEscapeCommand(AnsiOutputStream.java:352) at hudson.plugins.ansicolor.AnsiOutputStream.write(AnsiOutputStream.java:138) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.write(AnsiHtmlOutputStream.java:220) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:55) at hudson.plugins.ansicolor.ColorConsoleAnnotator.annotate(ColorConsoleAnnotator.java:91) at hudson.console.ConsoleAnnotator$ConsoleAnnotatorAggregator.annotate(ConsoleAnnotator.java:108) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:148) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1$1.write(FileLogStorage.java:238) at java.io.FilterOutputStream.write(FilterOutputStream.java:125) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:90) at org.kohsuke.stapler.framework.io.LargeText$HeadMark.moveTo(LargeText.java:314) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:229) at hudson.console.AnnotatedLargeText.writeRawLogTo(AnnotatedLargeText.java:163) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203) at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:144) at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:264) at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:92) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at
[JIRA] (JENKINS-55281) Error viewing build log
Title: Message Title
Gregor Philp edited a comment on JENKINS-55281
Re: Error viewing build log
we are also now seeing this same issue with some (but not all) builds. We are on jenkins version 2.150.1 When the build completes you can then see the console log but while its running you just get a stacktrace error page in jenkins.In the jenkins.log I see this{color:#ff}WARNING: Caught exception evaluating: it.writeLogTo(offset,output) in /job/ProSoft/job/GithubOrg/job/ProSoft/job/listingmanager-ui/job/staging%252F20180102/4/consoleFull. Reason: java.lang.IndexOutOfBoundsException{color}and{color:#de350b}Jan 02, 2019 9:47:25 PM org.eclipse.jetty.server.handler.ContextHandler$Context log{color}{color:#de350b}WARNING: Error while serving [/job/ProSoft/job/GithubOrg/job/ProSoft/job/listingmanager-ui/job/staging%252F20180102/2/logText/progressiveHtml| https://jenkins.moveaws.com/job/ProSoft/job/GithubOrg/job/ProSoft/job/listingmanager-ui/job/staging%252F20180102/2/logText/progressiveHtml ] {color}{color:#de350b}java.lang.reflect.InvocationTargetException{color}{color:#de350b} at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400){color}{color:#de350b} at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408){color}{color:#de350b} at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212){color}{color:#de350b} at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145){color}{color:#de350b} at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537){color}{color:#de350b} at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58){color}{color:#de350b} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739){color}{color:#de350b} at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870){color}{color:#de350b} at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221){color}{color:#de350b} at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58){color}{color:#de350b} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739){color}{color:#de350b} at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870){color}{color:#de350b} at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458){color}{color:#de350b} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739){color}{color:#de350b} at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870){color}{color:#de350b}/listingmanager{color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255){color}{color:#de350b} at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340){color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203){color}{color:#de350b} at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473){color}{color:#de350b} at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564){color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201){color}{color:#de350b} at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242){color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144){color}{color:#de350b} at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132){color}{color:#de350b} at org.eclipse.jetty.server.Server.handle(Server.java:503){color}{color:#de350b} at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364){color}{color:#de350b} at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260){color}{color:#de350b} at
[JIRA] (JENKINS-55281) Error viewing build log
Title: Message Title
Gregor Philp edited a comment on JENKINS-55281
Re: Error viewing build log
we are also now seeing this same issue with some (but not all) builds. We are on jenkins version 2.150.1 When the build completes you can then see the console log but while its running you just get a stacktrace error page in jenkins.In the jenkins.log I see this{color:# FF ff }WARNING: Caught exception evaluating: it.writeLogTo(offset,output) in /job/ProSoft/job/GithubOrg/job/ProSoft/job/listingmanager-ui/job/staging%252F20180102/4/consoleFull. Reason: java.lang.IndexOutOfBoundsException{color} and{color:#de350b}Jan 02, 2019 9:47:25 PM org.eclipse.jetty.server.handler.ContextHandler$Context log{color}{color:#de350b}WARNING: Error while serving https://jenkins.moveaws.com/job/ProSoft/job/GithubOrg/job/ProSoft/job/listingmanager-ui/job/staging%252F20180102/2/logText/progressiveHtml{color}{color:#de350b}java.lang.reflect.InvocationTargetException{color}{color:#de350b} at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400){color}{color:#de350b} at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408){color}{color:#de350b} at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212){color}{color:#de350b} at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145){color}{color:#de350b} at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537){color}{color:#de350b} at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58){color}{color:#de350b} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739){color}{color:#de350b} at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870){color}{color:#de350b} at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221){color}{color:#de350b} at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58){color}{color:#de350b} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739){color}{color:#de350b} at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870){color}{color:#de350b} at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458){color}{color:#de350b} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739){color}{color:#de350b} at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870){color}{color:#de350b}/listingmanager{color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255){color}{color:#de350b} at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340){color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203){color}{color:#de350b} at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473){color}{color:#de350b} at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564){color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201){color}{color:#de350b} at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242){color}{color:#de350b} at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144){color}{color:#de350b} at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132){color}{color:#de350b} at org.eclipse.jetty.server.Server.handle(Server.java:503){color}{color:#de350b} at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364){color}{color:#de350b} at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260){color}{color:#de350b} at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305){color}{color:#de350b} at
[JIRA] (JENKINS-55281) Error viewing build log
Title: Message Title Gregor Philp updated an issue Jenkins / JENKINS-55281 Error viewing build log Change By: Gregor Philp Attachment: Screen Shot 2019-01-02 at 2.26.23 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55281) Error viewing build log
Title: Message Title Gregor Philp commented on JENKINS-55281 Re: Error viewing build log we are also now seeing this same issue with some (but not all) builds. We are on jenkins version 2.150.1 When the build completes you can then see the console log but while its running you just get a stacktrace error page in jenkins. In the jenkins.log I see this WARNING: Caught exception evaluating: it.writeLogTo(offset,output) in /job/ProSoft/job/GithubOrg/job/ProSoft/job/listingmanager-ui/job/staging%252F20180102/4/consoleFull. Reason: java.lang.IndexOutOfBoundsException I see this was a bug some time ago that was fixed but appears to be happening again. JENKINS-29179 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Gregor Philp edited a comment on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Hi, we have the same issue still on CentOS Linux 6 and 7 platforms. We'd like these to just be removed and not reported so that we have to manually remove them. We end up with 100s, 1000s of these. !Screen Shot 2017-01-09 at 3.46.57 PM.png|thumbnail! We have latest plugin versions:Workspace Cleanup Plugin - 0.32Resource Disposer Plugin - 0.3and running jenkins master - 2.19.4 It seems this might be related to the problem we're having of the java heap being used up and then our master fails. I then have to restart master.thanksGregor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Gregor Philp commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Hi, we have the same issue still on CentOS Linux 6 and 7 platforms. We'd like these to just be removed and not reported so that we have to manually remove them. We end up with 100s, 1000s of these. It seems this might be related to the problem we're having of the java heap being used up and then our master fails. I then have to restart master. thanks Gregor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Gregor Philp updated an issue Jenkins / JENKINS-24824 Asynchronous cleanup not removing renamed workspace directories on slaves Change By: Gregor Philp Attachment: Screen Shot 2017-01-09 at 3.46.57 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
