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

Polling with excluded regions don't prevent job triggered

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin
    • None
    • Git plugin 2.0

      I've three jobs that trigger git with the same repository and branch.
      In then Excluded Regions I add specific folders for each job.

      Example:
      project/common
      project/projectA
      project/projectB
      project/projectC

      If I made change on projectB folder, all the three job are build.

          [JENKINS-20569] Polling with excluded regions don't prevent job triggered

          Anthony FLORANT created issue -

          Mark Waite added a comment -

          I attempted various combinations of patterns and could not find any pattern which would exclude all the changes in a subdirectory (like project/common). The behavior was the same for the JGit and the command line implementations.

          I'm reasonably confident this worked in the past, since we used it with older versions of the plugin.

          Mark Waite added a comment - I attempted various combinations of patterns and could not find any pattern which would exclude all the changes in a subdirectory (like project/common). The behavior was the same for the JGit and the command line implementations. I'm reasonably confident this worked in the past, since we used it with older versions of the plugin.

          This feature worked at our location in the 1.4 version of the plugin.
          When I upgraded to the 2.0 version of the plugin, I experienced the issue listed above. The value that was formerly in 'Included Regions' was still present...but, it didn't result in the polling to be specific to the directory.
          So, I downgraded back to the 1.4 version of the plugin in hopes of getting the functionality back. Unfortunately, when I downgraded, the value present in the 'Included Regions' disappeared. Yikes.

          Sonia Shepherd added a comment - This feature worked at our location in the 1.4 version of the plugin. When I upgraded to the 2.0 version of the plugin, I experienced the issue listed above. The value that was formerly in 'Included Regions' was still present...but, it didn't result in the polling to be specific to the directory. So, I downgraded back to the 1.4 version of the plugin in hopes of getting the functionality back. Unfortunately, when I downgraded, the value present in the 'Included Regions' disappeared. Yikes.

          Mark Waite added a comment -

          Sonia, the 2.0 release was a major release which included changes to the job definition XML file. Those changes make the new data values unreadable by the old plugin. You will probably need to restore an old copy of the job definition XML file (jobs/<jobname>/config.xml).

          Mark Waite added a comment - Sonia, the 2.0 release was a major release which included changes to the job definition XML file. Those changes make the new data values unreadable by the old plugin. You will probably need to restore an old copy of the job definition XML file (jobs/<jobname>/config.xml).

          Yesterday, I downgrade from 2.0 to 1.5.
          Exculded regions work as expected but included regions as no effect.
          If I set "projector/.*\.cpp" in the included regions and I changed a .txt in git, a job was triggered...

          Anthony FLORANT added a comment - Yesterday, I downgrade from 2.0 to 1.5. Exculded regions work as expected but included regions as no effect. If I set "projector/.*\.cpp" in the included regions and I changed a .txt in git, a job was triggered...
          Liya Katz made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]

          Joe Mihalich added a comment - - edited

          I am having the exact same issue with included regions not being honored. Every job on the branch that git sends gets built regardless of what's in the included regions. Was on 1.4 before this and it was working great.

          I have to downgrade to 1.4.0 because of this bug. I can't have the entire project building every time one file changes. Please fix this ASAP.

          Joe Mihalich added a comment - - edited I am having the exact same issue with included regions not being honored. Every job on the branch that git sends gets built regardless of what's in the included regions. Was on 1.4 before this and it was working great. I have to downgrade to 1.4.0 because of this bug. I can't have the entire project building every time one file changes. Please fix this ASAP.

          This happens due to remote polling. This is also the case with 1.x when remote polling is set
          By nature, remote polling only can compare remote HEAD with last build sha1, not consider commit filters

          Nicolas De Loof added a comment - This happens due to remote polling. This is also the case with 1.x when remote polling is set By nature, remote polling only can compare remote HEAD with last build sha1, not consider commit filters

          Joe Mihalich added a comment -

          I don't understand that. This feature was working fine in the 1.4.0 git plugin. Something must have been broken.

          Joe Mihalich added a comment - I don't understand that. This feature was working fine in the 1.4.0 git plugin. Something must have been broken.

          Erik Cokeley added a comment - - edited

          I also need the Included Regions. This is failing for me and many builds are being kicked off; I'm not sure if all my builds within the git and branch but at least many. What version has Included Region (or excluded region) working?

          Erik Cokeley added a comment - - edited I also need the Included Regions. This is failing for me and many builds are being kicked off; I'm not sure if all my builds within the git and branch but at least many. What version has Included Region (or excluded region) working?

            Unassigned Unassigned
            anthony Anthony FLORANT
            Votes:
            13 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: