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

Perforce triggered build should not trigger polling on jobs unless there are changes related to that view

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None

      The current implementation triggers polling on all jobs with Perforce Triggered Build enabled. This is fine for small installations with few check ins per day, but not for installations with hundreds of jobs. This can cause massive spikes in size increases for Perforce server logs.

      For example, if I check in a file to "//my_depot/..." I should trigger polling on a job with view:

      //my_depot/... //workspace_name/...

      However, I should not trigger polling on a job with view:

      //my_depot2/... //workspace_name/...

          [JENKINS-41764] Perforce triggered build should not trigger polling on jobs unless there are changes related to that view

            Unassigned Unassigned
            rpocase Robby Pocase
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: