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

Jobs are triggered when no scm (perforce) changes are reported


    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • p4-plugin
    • None
    • Master node with five slaves running on linux with latest Perforce scm plugin installed

      After upgrading from 1.339 to 1.381 then to 1.386 our build farm is grinding to a halt. Jobs continue to be triggered when no scm changes are made. We have a huge number of configured jobs which keep being scheduled to build as the scm polling is somehow detecting changes even though nothing is changing. Our queues continue to grow which affects the performance of the farm.

      Basically when I drill down into a job it reports No changes from last build. but when I view the scm poll history it reports Changes found

      The latest P4 plugin is installed

            Unassigned Unassigned
            rbracewell rbracewell
            0 Vote for this issue
            3 Start watching this issue