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

Inefficient trigger code when there is a large number of jobs/PR triggers in Jenkins

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ghprb-plugin
    • None

      In large Jenkins installations with large numbers of jobs and pull request triggers, the doIndex code ends up being fairly inefficient for processing the github pull request messages. For each type of message, the entire project list is walked and a new GhprbWebHook object is allocated (twice in cases where it is actually needed).

      As the number of projects in our instance has grown, it more and more time to trigger each build.

            Unassigned Unassigned
            mmitche Matthew Mitchell
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: