[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer commented on JENKINS-12967 Cannot view HTML report for a specific build. Thanks! Regarding the ant pattern in 1.1: as far as I understood is the ant pattern only used for the actual files, which must reside in the same directory. My use case was multiple files in multiple directories. Thanks again Carsten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
mcrooney commented on JENKINS-12967 Cannot view HTML report for a specific build. That makes more sense, got it, thanks! I'll release this as 1.1, which looking at the unreleased changes, will include Ant pattern support. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
SCM/JIRA link daemon commented on JENKINS-12967 Cannot view HTML report for a specific build. Code changed in jenkins User: Michael Rooney Path: src/main/java/htmlpublisher/HtmlPublisher.java src/main/java/htmlpublisher/HtmlPublisherTarget.java http://jenkins-ci.org/commit/htmlpublisher-plugin/1c947aaf9457010fd403da8e345ea3ec96441510 Log: apply patch from https://issues.jenkins-ci.org/browse/JENKINS-12967 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
SCM/JIRA link daemon commented on JENKINS-12967 Cannot view HTML report for a specific build. Code changed in jenkins User: Michael Rooney Path: src/main/java/htmlpublisher/HtmlPublisher.java src/main/java/htmlpublisher/HtmlPublisherTarget.java http://jenkins-ci.org/commit/htmlpublisher-plugin/80f54d668997d3cbd1a8e110a2ac4f93ee391b64 Log: Revert "apply patch from https://issues.jenkins-ci.org/browse/JENKINS-12967" This reverts commit 1c947aaf9457010fd403da8e345ea3ec96441510. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
SCM/JIRA link daemon commented on JENKINS-12967 Cannot view HTML report for a specific build. Code changed in jenkins User: Mike Rooney Path: src/main/java/htmlpublisher/HtmlPublisherTarget.java http://jenkins-ci.org/commit/htmlpublisher-plugin/a6ad78e1b85a0069a9b6d1060e2d63364e1ec568 Log: Merge pull request #7 from mrooney/master JENKINS-12967 Compare: https://github.com/jenkinsci/htmlpublisher-plugin/compare/75f78184d2cf...a6ad78e1b85a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
mcrooney commented on JENKINS-12967 Cannot view HTML report for a specific build. Okay, thanks Carsten, I've applied the patch to a fork and submitted a pull request. If the build passes I can merge it in. Would this patch change any functionality or simply fix the bug? Thanks again for your contribution! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
mcrooney commented on JENKINS-12967 Cannot view HTML report for a specific build. Actually this patch appears to introduce a syntax error, due to line 108 of fix.patch, the empty "File" line. Let me know if I can just delete that line or if the patch is incomplete. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer commented on JENKINS-12967 Cannot view HTML report for a specific build. D'oh, I'm so sorry. The patch contained stuff that was not meant to be in there. It appears as though the Eclipse egit plugin created the patch for the entire project instead of just the single file that I had selected. The patch should be tiny and contain only the change in HtmlPublisherTarget.java (i.e. the new method getOwner()). The other changes were an attempt to support reports in arbitrary directories, to be specified by an ant pattern. Please disregard that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer updated JENKINS-12967 Cannot view HTML report for a specific build. This patch fixes it for me. Change By: Carsten Pfeiffer (30/Nov/12 8:59 PM) Attachment: fix.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer edited a comment on JENKINS-12967 Cannot view HTML report for a specific build. I have the same issue with Jenkins 1.488. And it appears to be the same problem as JENKINS-14625. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Antti Andreimann commented on JENKINS-12967 Cannot view HTML report for a specific build. I see the same issue if I set the document to *.log If I set it to specific filenames, the problem disappears. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer commented on JENKINS-12967 Cannot view HTML report for a specific build. I have the same issue with Jenkins 1.488. And it appears to be the same problem as JENKINS-12967. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Nathmie S created JENKINS-12967: --- Summary: Cannot view HTML report for a specific build. Key: JENKINS-12967 URL: https://issues.jenkins-ci.org/browse/JENKINS-12967 Project: Jenkins Issue Type: Bug Components: htmlpublisher Reporter: Nathmie S Assignee: mcrooney I get the following error when trying to view a HTML report for a specific build. I have 'keep history' checkbox on. I then execute a build and once compelted view the html report and get the following. I checked in the folder structure. C:\jenkins\jobs\Antie\builds\2012-03-02_16-53-55\htmlreports\HTML_Reports\ exists The URL it is trying to show is: http://localhost:8080/job/Antie/68/HTML_Reports/? Status Code: 500 Exception: Stacktrace: org.apache.commons.jelly.JellyTagException: jar:file:/C:/jenkins/war/WEB-INF/lib/jenkins-core-1.452.jar!/hudson/model/DirectoryBrowserSupport/dir.jelly:29:58: st:include No page found 'sidepanel.jelly' for class htmlpublisher.HtmlPublisherTarget$HTMLBuildAction at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:247) at hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:108) at htmlpublisher.HtmlPublisherTarget$BaseHTMLAction.doDynamic(HtmlPublisherTarget.java:130) at htmlpublisher.HtmlPublisherTarget$HTMLBuildAction.doDynamic(HtmlPublisherTarget.java:170) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:363) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at
