-
Bug
-
Resolution: Fixed
-
Critical
-
None
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.
[JENKINS-13580] git plugin "included regions" feature is bypassed when evaluating a merge commit
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 144047 ] | New: JNJira + In-Review [ 190879 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
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