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

Git plugin ignores included/excluded paths when triggering build on commit notification

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • git-plugin
    • None

      I have a Git repository, which contains of multiple modules, which should be build separately. I have separate Jenkins job for each module. Stash's "Jenkins Webhook plugin" notifies Jenkins about a new commit, which triggers ALL the module job to start.
      To separate job I've used "polling ignores commits in certain paths", selecting included regions. Seems, like the regions are not used during commit notification triggering.

          [JENKINS-25048] Git plugin ignores included/excluded paths when triggering build on commit notification

          Pavel Baranchikov created issue -

          Mark Waite added a comment -

          If you've not already configured the job to force polling using workspace, you may want to try that.

          Mark Waite added a comment - If you've not already configured the job to force polling using workspace, you may want to try that.

          I tried, but this does not help. According to the code, the plugins check had not been implemented for notifyCommit URL at all. Please, take a look at https://github.com/jenkinsci/git-plugin/pull/263.

          Pavel Baranchikov added a comment - I tried, but this does not help. According to the code, the plugins check had not been implemented for notifyCommit URL at all. Please, take a look at https://github.com/jenkinsci/git-plugin/pull/263 .
          Kanstantsin Shautsou made changes -
          Labels New: git-plugin-PathRestriction

          Code changed in jenkins
          User: Pavel Baranchikov
          Path:
          src/main/java/hudson/plugins/git/GitSCM.java
          src/main/java/hudson/plugins/git/GitStatus.java
          src/test/java/hudson/plugins/git/GitSCMTest.java
          http://jenkins-ci.org/commit/git-plugin/70da6b90b4cbd2097ac51552e8169034472959c4
          Log:
          JENKINS-25048: Added filters check for notifyCommit event

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Pavel Baranchikov Path: src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/GitStatus.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/70da6b90b4cbd2097ac51552e8169034472959c4 Log: JENKINS-25048 : Added filters check for notifyCommit event

          Code changed in jenkins
          User: Pavel Baranchikov
          Path:
          src/main/java/hudson/plugins/git/GitSCM.java
          src/main/java/hudson/plugins/git/GitStatus.java
          src/test/java/hudson/plugins/git/GitSCMTest.java
          http://jenkins-ci.org/commit/git-plugin/dae26dc8d01bd457aa84fdbcdb755c7fdbc5458f
          Log:
          JENKINS-25048: Added filters check for notifyCommit event

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Pavel Baranchikov Path: src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/GitStatus.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/dae26dc8d01bd457aa84fdbcdb755c7fdbc5458f Log: JENKINS-25048 : Added filters check for notifyCommit event

          So this is a major issue for us as well. We are trying to put build job config in source. Right now with commit notifications, we cannot ignore that repository directory with this bug currently active.

          nick carpenter added a comment - So this is a major issue for us as well. We are trying to put build job config in source. Right now with commit notifications, we cannot ignore that repository directory with this bug currently active.

          This is a blocker for us too - different modules in different folders - needs to get this bug fixed. Please let us know if there are any work arounds..

          Sunish Vengathattil added a comment - This is a blocker for us too - different modules in different folders - needs to get this bug fixed. Please let us know if there are any work arounds..

          Mark Waite added a comment -

          No work around that I recognize.

          Mark Waite added a comment - No work around that I recognize.
          Daniel Beck made changes -
          Labels Original: git-plugin-PathRestriction

            Unassigned Unassigned
            pbaranchikov Pavel Baranchikov
            Votes:
            30 Vote for this issue
            Watchers:
            37 Start watching this issue

              Created:
              Updated: