[
https://issues.apache.org/jira/browse/COMDEV-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-168.
-------------------------
Resolution: Invalid
Turns out the data was being fetched by a cron job (readjira.py) apart from the
projects.json file. This is now also done by that script.
However, when a new project is added, its JIRA file has to be fetched the first
time; after that it should be fetched by the cron job.
> getjson.py fetches everything each time
> ---------------------------------------
>
> Key: COMDEV-168
> URL: https://issues.apache.org/jira/browse/COMDEV-168
> Project: Community Development
> Issue Type: Bug
> Components: Reporter Tool
> Reporter: Sebb
>
> The reporter tool uses the script getjson.py to fetch various items of data
> for each of the projects to which the login has access.
> However some of the data is expensive to fetch, e.g. the JIRA data.
> This is done even if the user does not click on the tab.
> Although the data is cached, it can only be cached for a short time
> (currently 2 days is used).
> For logins who are members of multiple projects that use JIRA, it can take so
> long to fetch the JIRA info that the CGI script times out. Retrying will
> eventually allow the app to work. [e.g. a member of Commons will potentially
> need to download 50 JIRA statistics]
> It would be better if the data were only fetched when needed, though this
> would still cause issues for PMCs like Commons.
> Alternatively, the data could be fetched by a cron job.
> A disadvantage is that the data might be fetched even when it is not going to
> be used. Note: the cron job could/should be scheduled for times when JIRA is
> not as busy; also it could be set to run relatively slowly (i.e. with pauses
> between fetches).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
