Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-23352

Build monitor plugin slow to open config page with lots of jobs

      We have a Jenkins server with ~1,100 jobs. It takes over 50 seconds just to open the config page for any Build Monitor Plugin view. That's far too slow.

          [JENKINS-23352] Build monitor plugin slow to open config page with lots of jobs

          Jan Molak added a comment -

          Hi Jonathan and thanks for your feedback, would you mind raising this issue using the official issue tracker on Github?
          https://github.com/jan-molak/jenkins-build-monitor-plugin/issues?state=open

          Also, have you considered using the Cloudbees folder plugin to group those ~1,100 jobs?
          https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin

          Many thanks,
          Jan

          Jan Molak added a comment - Hi Jonathan and thanks for your feedback, would you mind raising this issue using the official issue tracker on Github? https://github.com/jan-molak/jenkins-build-monitor-plugin/issues?state=open Also, have you considered using the Cloudbees folder plugin to group those ~1,100 jobs? https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin Many thanks, Jan

          Issued has been filed at https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/74. Sorry about that. It's REALLY hard for an outsider to figure out the "right" place to file issues about each individual plugin...

          Jonathan Brecher added a comment - Issued has been filed at https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/74 . Sorry about that. It's REALLY hard for an outsider to figure out the "right" place to file issues about each individual plugin...

          Jan Molak added a comment -

          No worries; Jenkins Wiki "plugin info" box points to Jenkins Jira ticketing system by default and, from what I can tell, can't be configured to point to Github.

          Build Monitor wiki page mentions that the plugin uses Github issues instead of the default ones, but perhaps this information should be more prominent?

          Best,
          J

          Jan Molak added a comment - No worries; Jenkins Wiki "plugin info" box points to Jenkins Jira ticketing system by default and, from what I can tell, can't be configured to point to Github. Build Monitor wiki page mentions that the plugin uses Github issues instead of the default ones, but perhaps this information should be more prominent? Best, J

            Unassigned Unassigned
            jonathanb Jonathan Brecher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: