[JIRA] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Ramin: that's also a good idea, but I've fixed this one by the caching solution now. Please create an improvement issue, if you think your idea is additionally needed. 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi resolved JENKINS-18155 as Fixed Recent changes view slow because of JIRA plugin Fixed in https://github.com/jenkinsci/jira-plugin/commit/ab5aad99ce881520369c9c6d49c069878ba4a7dc Change By: kutzi (10/Jul/13 3:04 PM) 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
Ramin Baradari edited a comment on JENKINS-18155 Recent changes view slow because of JIRA plugin Why do we fetch the data for all issues up front at all? Most of the time we just want to skim the change log and read a few select or none of the descriptions at all. Idea: Just annotate each matching issue id with a link to the issue page in JIRA (without any checks if it is actually a known issue in JIRA) and an on-hover handler that fetches the issue summary on demand. I think this is what the Bugzilla annotator does/did. 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
Ramin Baradari commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Why do we fetch the data for all issues up front at all? Most of the time we just want to skim the change log and read a few select or none of the descriptions at all. Idea: Just annotate each matching issue id with a link to the issue page in JIRA (without any checks if it is actually a known issue in JIRA) and an on hover handler that does fetches the issue summary on demand. I think this is what the Bugzilla annotator does/did. 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi created JENKINS-18155 Recent changes view slow because of JIRA plugin Issue Type: Improvement Assignee: Unassigned Components: jira Created: 31/May/13 7:53 AM Description: When displaying the changes view when you have many changes with associated JIRA tickets, the operation can be quite slow. Seems like the JiraChangeLogAnnotator is trying to get each JIRA issue in a single call, even if the issue has already been fetched previously - e.g. because another change already had the same issue Project: Jenkins Priority: Major Reporter: kutzi 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Thread dump: Handling GET /job/X/changes : RequestHandlerThread22349 "Handling GET /job/X/changes : RequestHandlerThread22349" Id=1061466 Group=main RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) locked java.io.BufferedInputStream@78cdd495 at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at hudson.plugins.jira.soap.JirasoapserviceV2SoapBindingStub.getIssue(JirasoapserviceV2SoapBindingStub.java:3881) at hudson.plugins.jira.JiraSession.getIssue(JiraSession.java:120) at hudson.plugins.jira.JiraSite.getIssue(JiraSite.java:293) at hudson.plugins.jira.JiraChangeLogAnnotator.annotate(JiraChangeLogAnnotator.java:72) at hudson.scm.ChangeLogSet$Entry.getMsgAnnotated(ChangeLogSet.java:210) at sun.reflect.GeneratedMethodAccessor766.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly.tags.core.ExprTag.doTag(ExprTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrar
[JIRA] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi assigned JENKINS-18155 to kutzi Recent changes view slow because of JIRA plugin Change By: kutzi (31/May/13 7:56 AM) Assignee: kutzi 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Idea: cache recently accessed issues 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Wondering why it seems to be so slow on every display - shouldn't the issues be saved to the build after the 1st display? 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.
