|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I too have been experiencing similar problems with the Jenkins dashboard. I'm using the latest release as of last week (1.513). The problem seems to arise once a build / job has begun. Navigating the dashboard otherwise seems fine, but when a build kicks in it can take minutes for the dashboard to respond. Even just running a single job with minimal load on the system (e.g.: < 10% CPU usage) the dashboard becomes unusable, even on a high-end development machine (e.g.: Win7 x64, i7 3.4Ghz, 16GB RAM, SSD, etc.)
Now I have been unable to find any log files in the Jenkins home folder that include the level of detail others are reporting above. Perhaps I need to increase the verbosity level somewhere in the Jenkins configuration. If anyone could suggest where to look for that I'd appreciate it.