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

Excluded-regions doesn't work properly with merges

      Until the included-regions feature is ready, we're using excluded-regions with a negative regexp to simulate it. example: ^(?!plugins/my-plugin-0.1\/).+$

      We have the git plugin building straight off a branch and are not using merge before build. The behavior I'm seeing is that if I push commits directly to that branch this works great, but if the HEAD of that branch refers to a merge commit, the build ALWAYS thinks it ought to build, even if no changes were registered that weren't excluded by the regexp.

          [JENKINS-8014] Excluded-regions doesn't work properly with merges

          sirlyric created issue -
          Kanstantsin Shautsou made changes -
          Labels New: git-plugin-PathRestriction
          Kanstantsin Shautsou made changes -
          Labels Original: git-plugin-PathRestriction New: GitSCMExtension git-plugin-PathRestriction
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 138117 ] New: JNJira + In-Review [ 174824 ]
          Mark Waite made changes -
          Assignee Original: Andrew Bayer [ abayer ]

            Unassigned Unassigned
            sirlyric sirlyric
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: