[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2014-08-28 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 updated  JENKINS-18498


TestNG reports not working on specific build.
















Change By:


Jesse Glick
(28/Aug/14 3:11 PM)




Labels:


plugin,testng



























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







-- 
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] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-29 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-18498


TestNG reports not working on specific build.















Code changed in jenkins
User: Nalin Makar
Path:
 README
 src/main/java/hudson/plugins/testng/results/BaseResult.java
 src/main/java/hudson/plugins/testng/results/TestNGResult.java
http://jenkins-ci.org/commit/testng-plugin-plugin/8be94c3db0a4305527a25a8d709e91bb9caf2213
Log:
  Fixed: JENKINS-18498 -  hudson.tasks.test.AggregatedTestResultAction$1 cannot be cast to hudson.tasks.test.TestResult






























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







-- 
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/groups/opt_out.




[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-29 Thread nul...@nullin.com (JIRA)















































Nalin Makar
 assigned  JENKINS-18498 to Nalin Makar



TestNG reports not working on specific build.
















Change By:


Nalin Makar
(30/Jun/13 12:46 AM)




Assignee:


nalin_makar
NalinMakar



























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







-- 
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/groups/opt_out.




[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-29 Thread nul...@nullin.com (JIRA)















































Nalin Makar
 resolved  JENKINS-18498 as Fixed


TestNG reports not working on specific build.
















will be fixed in v1.2





Change By:


Nalin Makar
(30/Jun/13 12:46 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







-- 
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/groups/opt_out.




[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-28 Thread nul...@nullin.com (JIRA)














































Nalin Makar
 commented on  JENKINS-18498


TestNG reports not working on specific build.















Do you also have Junit Test Reports enabled on the same build at the same time as having TestNG Test Reports enabled?



























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







-- 
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/groups/opt_out.




[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-28 Thread nul...@nullin.com (JIRA)












































 
Nalin Makar
 edited a comment on  JENKINS-18498


TestNG reports not working on specific build.
















Do you also have Junit Test Reports enabled on the same build at the same time as having TestNG Test Reports enabled?

Also, is the job a Maven build or a Free Style build?



























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







-- 
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/groups/opt_out.




[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-25 Thread igonza...@nearsoft.com (JIRA)














































Jose Ignacio Gonzalez De La Fuente
 created  JENKINS-18498


TestNG reports not working on specific build.















Issue Type:


Bug



Affects Versions:


current



Assignee:


nalin_makar



Components:


testng



Created:


25/Jun/13 10:56 PM



Description:


The TestNG Results button works fine if we use it on the job screen (where we can see all the different jobs) but if you open a job and click on the TestNG Results button it will end up on a webpage not available. On both places it appends this to the URL /testngreports/?

This is the stack trace:
WARNING: Untrapped Error in Servlet
java.lang.RuntimeException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.518.jar!/lib/layout/layout.jelly:231:26: d:invokeBody org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.518.jar!/lib/layout/main-panel.jelly:36:21: d:invokeBody org.apache.commons.jelly.JellyTagException: hudson.tasks.test.AggregatedTestResultAction$1 cannot be cast to hudson.tasks.test.TestResult
at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:280)
at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92)
at $Proxy61.layout(Unknown Source)
at lib.LayoutTagLib$layout.call(Unknown Source)
at hudson.plugins.testng.TestNGTestResultBuildAction.index.run(index.groovy:8)
at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:69)
at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62)
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 org.kohsuke.stapler.jelly.groovy.GroovyFacet.handleIndexRequest(GroovyFacet.java:117)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
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:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
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 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at