Hi Stephane.

Perfect issue analysis. Here's the current flow during that XML RPC startup phase.

  • Retrieve project (a call to the XML RPC API that returns the project data)
  • Retrieve test plan and test cases (I believe it's a single call, or maybe one for the test plan and another for the test cases)
  • Filter only automated test cases (IIRC, it's done locally, since the API itself cannot handle it very well)
  • For each test case, retrieve the list of custom fields given in the job configuration page (yuck! I know, but ATM there is no way of retrieving all the test cases plus its custom fields in a single call).

Probably that's the reason why you're experiencing this problem.

Someone would have to change the current XML RPC API implementation in TestLink, and then we could reduce the number of HTTP requests in the plug-in.

Does that make sense?

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.
 
 

Reply via email to