[JIRA] (JENKINS-36180) Jenkins triggers build on git SCM changes even if nothing matches Includes regions
Title: Message Title Robin Kuivinen commented on JENKINS-36180 Re: Jenkins triggers build on git SCM changes even if nothing matches Includes regions We are having the same problem. Any progress on this ticket? Do you know any workaround for this issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36180) Jenkins triggers build on git SCM changes even if nothing matches Includes regions
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-36180 Jenkins triggers build on git SCM changes even if nothing matches Includes regions Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36180) Jenkins triggers build on git SCM changes even if nothing matches Includes regions
Title: Message Title
Jonas Thoursie updated an issue
Jenkins / JENKINS-36180
Jenkins triggers build on git SCM changes even if nothing matches Includes regions
Change By:
Jonas Thoursie
Hi!Our builds are set up to listen to changes on origin/master, and has "Included regions" configured. We are using Gitlab and makes heavy use of Merge Requests in Gitlab.When we do a merge, where the branch has pulled changed form master, the git-plugin says the following: { { quote} Ignored commit 906b26b2029df2242edb4a591d8ba2e855594be8: No paths matched included region whitelistDone. Took 4.5 secChanges found {quote } } No paths matched included whitelist, but it still triggers a build. I believe that this is because there are paths matching the included region whitelist, but they are in the commits that were in the merge from master->currentBranch. The reproduction steps: * Create 2 Jenkins jobs with different "Included regions whitelist"** Job 1: src/a** Job 2: src/b* Create new branch (myBranch)* Commit changes in `src/a`* Switch to master branch* Commit changes in `src/b`* Push changes* Switch to myBranch* Pull changes from master (git pull origin master)* Push changes * Create a merge request from myBranch to master (via Gitlab)* Accept merge requestThis triggers both Job1 AND Job2, even if I've only committed to Job1's Included region whitelist in my branch. I believe that this is not desired behaviour.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36180) Jenkins triggers build on git SCM changes even if nothing matches Includes regions
Title: Message Title
Jonas Thoursie created an issue
Jenkins / JENKINS-36180
Jenkins triggers build on git SCM changes even if nothing matches Includes regions
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Jun/23 9:41 AM
Labels:
gitlab git
Priority:
Critical
Reporter:
Jonas Thoursie
Hi! Our builds are set up to listen to changes on origin/master, and has "Included regions" configured. We are using Gitlab and makes heavy use of Merge Requests in Gitlab. When we do a merge, where the branch has pulled changed form master, the git-plugin says the following: {{Ignored commit 906b26b2029df2242edb4a591d8ba2e855594be8: No paths matched included region whitelist Done. Took 4.5 sec Changes found}} No paths matched included whitelist, but it still triggers a build. I believe that this is because there are paths matching the included region whitelist, but they are in the commits that were in the merge from master->currentBranch. The reproduction steps:
Create 2 Jenkins jobs with different "Included regions whitelist"
Job 1: src/a
Job 2: src/b
Create new branch (myBranch)
Commit changes in `src/a`
Switch to master branch
