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
-
-
- Open
-
- links to
Activity
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.
User exclusions are now working. This is from one of our pipelines:
Ignored commit 73adf973ee91ff5b21c0638878eee33df7204544: Found excluded author: Jenkins
Michael Andrews Good day. Can you please say more about how you got that working?
Michael Andrews 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.
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.