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

Git path polling ignores do not work in Pipeline jobs

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          Activity

            venh123 Venkatesh added a comment -

            Can anyone please confirm if this is working for Multibranch Pipeline jobs? Also, please provide some syntax. It's a humble request.

            venh123 Venkatesh added a comment - Can anyone please confirm if this is working for Multibranch Pipeline jobs? Also, please provide some syntax. It's a humble request.

            killdash9 I can get those log messages, however in situations where there is no actual workspace on a build node it still triggers the build (even though there's a duplicate workspace on the Jenkins master server). So I believe it works but still doesn't recognize using the master servers local copy as the source to make the determination. Which is not ideal.

            maxfields2000 Maxfield Stewart added a comment - killdash9 I can get those log messages, however in situations where there is no actual workspace on a build node it still triggers the build (even though there's a duplicate workspace on the Jenkins master server). So I believe it works but still doesn't recognize using the master servers local copy as the source to make the determination. Which is not ideal.
            rswanson Ron Swanson added a comment -

            killdash9 Good day. Can you please say more about how you got that working?

            rswanson Ron Swanson added a comment - killdash9 Good day. Can you please say more about how you got that working?

            User exclusions are now working. This is from one of our pipelines:

            Ignored commit 73adf973ee91ff5b21c0638878eee33df7204544: Found excluded author: Jenkins
            
            killdash9 Michael Andrews added a comment - User exclusions are now working. This is from one of our pipelines: Ignored commit 73adf973ee91ff5b21c0638878eee33df7204544: Found excluded author: Jenkins
            jglick Jesse Glick added a comment -

            It is well known that you cannot use path exclusions when Git is configured to perform master-based polling, due to limitations in the Git network protocol. Would be solvable only by using a master repo cache the way the Mercurial plugin does, and in fact git already does for multibranch projects. I think this is already filed somewhere.

            Polling exclusions are not currently supported for multibranch projects under any circumstances. That is probably also already filed somewhere.

            jglick Jesse Glick added a comment - It is well known that you cannot use path exclusions when Git is configured to perform master-based polling, due to limitations in the Git network protocol. Would be solvable only by using a master repo cache the way the Mercurial plugin does, and in fact git already does for multibranch projects. I think this is already filed somewhere. Polling exclusions are not currently supported for multibranch projects under any circumstances. That is probably also already filed somewhere.

            People

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

              Dates

                Created:
                Updated:
                Resolved: