Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Component/s: git-plugin, multi-branch-project-plugin (not Pipeline)
-
Labels:
-
Environment:Jenkins LTS 2.7.1
Ubuntu 12.04
Git Plugin 2.5.2
Pipeline Plugin 2.2
-
Similar Issues:
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
- duplicates
-
JENKINS-36195 Pipeline polling ignores special polling rules
-
- Open
-
- links to
Path inclusions and exclusions (in a NON-MULTIBRANCH project) seem to work fine when there is a persistent workspace (we use the master to Checkout all code - then move on to a worker node). This is the case in NON-PIPELINE jobs as well and has been as such for some time. The USER inclusion/exclusion do not work in pipelines. Definitely Hoping for a fix to the user exclusions soon as our automated tagging and version bumping always results in a new build.