[
https://issues.jenkins-ci.org/browse/JENKINS-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163036#comment-163036
]
Bertrand Latinville commented on JENKINS-13580:
-----------------------------------------------
This problem could be linked with the issue I raised
where multiple commits in one push are not taken into account.
https://issues.jenkins-ci.org/browse/JENKINS-13368
> git plugin "included regions" feature is bypassed when evaluating a merge
> commit
> --------------------------------------------------------------------------------
>
> Key: JENKINS-13580
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13580
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Reporter: Nathan Mehl
> Priority: Critical
> Attachments: config.xml
>
>
> If the built branch is updated via a merge commit rather than a change, the
> build is triggered regardless of whether the files updated in the merge match
> the included regions regexp or not.
> A test repo can be found at
> http://blank.org/memory/work/jenkins-bug/repo/jenkins-bug/regions-test.git.
> A config.xml is attached to this ticket. Note that commit
> 10c1279f32a5ffe9f6eabfe01aa360341144c263 in that repo (merge
> testbranch->master) triggers a build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
