-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins - 1.580.3, Git Plugin - 2.4.1 (was seen in 2.4.0) too,
We use Polling Ignores Commits in Certain Paths option to poll for changes in a specific directory of the git repo. It works smooth until we merge changes from another branch onto the polled branch.
Even though the merged changes don't come under the Included Regions, builds get triggered.
Job Config looking for changes only under "harsha" directory.
Build triggered by changes polled under a different directory
Ideally even when the merge happens, the plugin should trigger changes based on the included regions.
Browsing on this page because I have the exactly same issue: we have a repo with multiple libraries, each in a subdirectory:
We have a job per library polling changes in the matching subdirectory. I all works fine with normal commits, but fails when a merge is done from another branch.
I.e. if I commit to master (the branch we are polling) a change to a file inside the subdir "library1", then only the associated job is triggered as expected.
If I create a branch "awesome-feature-for-library1" and inside that branch edit a file inside the subdir "library1" and create a PR (we are using github) that is merged, then the jobs for each lib is called (while only the job associated to "library1" is expected to run.
We are using: