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

Git path polling ignores do not work in Pipeline jobs

XMLWordPrintable

      Multibranch pipeline jobs seem to ignore git path polling rules when attempting to detect indexing changes and schedule builds.

      More specifically:

      • I am using a "Periodically if not otherwise run" build trigger
      • I tested "Git polling ignores commits in certain paths" with the following:

      1) Only including paths that I care about:
      Included:
      that-path-I-care-about/.*
      Excluded:
      (empty)

      2) Including paths I care about and excluding a specific path:
      Included:
      that-path-I-care-about/.*
      Excluded:
      that-path-I-want-to-ignore/.*

      3) Just using excluded paths:
      Included:
      (empty)
      Excluded:
      that-path-I-want-to-ignore/.*

      None of them work as expected. Builds are triggered anytime a change is committed to the repo.

          [JENKINS-36836] Git path polling ignores do not work in Pipeline jobs

          Preston Jennings created issue -
          Preston Jennings made changes -
          Description Original: Multibranch pipeline jobs seem to ignore git polling rules when attempting to detect indexing changes and scheduling builds.

          More specifically:
          - I am using a "Periodically if not otherwise run" build trigger
          - I tested "Git polling ignores commits in certain paths" with the following:

          1) Only including paths that I care about:
          Included:
          that-path-I-care-about/.*
          Excluded:
          (empty)

          2) Including paths I care about and excluding a specific path:
          Included:
          that-path-I-care-about/.*
          Excluded:
          that-path-I-want-to-ignore/.*

          3) Just using excluded paths:
          Included:
          (empty)
          Excluded:
          that-path-I-want-to-ignore/.*

          None of them work as expected. Builds are triggered anytime a change is committed to the repo.           		New: Multibranch pipeline jobs seem to ignore git polling rules when attempting to detect indexing changes and schedule builds.

          More specifically:
          - I am using a "Periodically if not otherwise run" build trigger
          - I tested "Git polling ignores commits in certain paths" with the following:

          1) Only including paths that I care about:
          Included:
          that-path-I-care-about/.*
          Excluded:
          (empty)

          2) Including paths I care about and excluding a specific path:
          Included:
          that-path-I-care-about/.*
          Excluded:
          that-path-I-want-to-ignore/.*

          3) Just using excluded paths:
          Included:
          (empty)
          Excluded:
          that-path-I-want-to-ignore/.*

          None of them work as expected. Builds are triggered anytime a change is committed to the repo.
          Preston Jennings made changes -
          Summary Original: Git polling ignores do not work in Multibranch Pipeline job New: Git path polling ignores do not work in Multibranch Pipeline job
          Preston Jennings made changes -
          Description Original: Multibranch pipeline jobs seem to ignore git polling rules when attempting to detect indexing changes and schedule builds.

          More specifically:
          - I am using a "Periodically if not otherwise run" build trigger
          - I tested "Git polling ignores commits in certain paths" with the following:

          1) Only including paths that I care about:
          Included:
          that-path-I-care-about/.*
          Excluded:
          (empty)

          2) Including paths I care about and excluding a specific path:
          Included:
          that-path-I-care-about/.*
          Excluded:
          that-path-I-want-to-ignore/.*

          3) Just using excluded paths:
          Included:
          (empty)
          Excluded:
          that-path-I-want-to-ignore/.*

          None of them work as expected. Builds are triggered anytime a change is committed to the repo.           		New: Multibranch pipeline jobs seem to ignore git path polling rules when attempting to detect indexing changes and schedule builds.

          More specifically:
          - I am using a "Periodically if not otherwise run" build trigger
          - I tested "Git polling ignores commits in certain paths" with the following:

          1) Only including paths that I care about:
          Included:
          that-path-I-care-about/.*
          Excluded:
          (empty)

          2) Including paths I care about and excluding a specific path:
          Included:
          that-path-I-care-about/.*
          Excluded:
          that-path-I-want-to-ignore/.*

          3) Just using excluded paths:
          Included:
          (empty)
          Excluded:
          that-path-I-want-to-ignore/.*

          None of them work as expected. Builds are triggered anytime a change is committed to the repo.
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]
          mcrooney made changes -
          Summary Original: Git path polling ignores do not work in Multibranch Pipeline job New: Git path polling ignores do not work in Pipeline jobs

          mcrooney added a comment -

          Seeing this as well on a normal pipeline job, so I don't believe it is specific to multibranch ones. Perhaps the issue has something to do with the way workspaces are handled for Pipeline jobs? I posted about it here: https://groups.google.com/forum/#!msg/jenkinsci-users/wNIMGhJ76rA/HddRoHW-CAAJ

          mcrooney added a comment - Seeing this as well on a normal pipeline job, so I don't believe it is specific to multibranch ones. Perhaps the issue has something to do with the way workspaces are handled for Pipeline jobs? I posted about it here: https://groups.google.com/forum/#!msg/jenkinsci-users/wNIMGhJ76rA/HddRoHW-CAAJ
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 173579 ] New: JNJira + In-Review [ 185209 ]

          Jesse Glick added a comment -

          Sounds like a duplicate.

          Jesse Glick added a comment - Sounds like a duplicate.
          Jesse Glick made changes -
          Link New: This issue duplicates JENKINS-36195 [ JENKINS-36195 ]
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            prestonj Preston Jennings
            Votes:
            21 Vote for this issue
            Watchers:
            35 Start watching this issue

              Created:
              Updated:
              Resolved: