[JIRA] (JENKINS-22457) Git push will trigger a build even though no path matches included regions

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-22457

Jenkins / JENKINS-22457 Git push will trigger a build even though no path matches included regions Change By: Mark Waite Status: Reopened Open Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[nicolas.deloof@gmail.com (JIRA)]

Nicolas De Loof assigned an issue to Unassigned

Jenkins / JENKINS-22457 Git push will trigger a build even though no path matches included regions

Change By: Nicolas De Loof Assignee: Nicolas De Loof

Add Comment

[kanthak@freenet.de (JIRA)]

Christian Kanthak commented on JENKINS-22457

Re: Git push will trigger a build even though no path matches included regions Just a note for others visiting this page because they have problems with 'included-regions' as I had: I also had trouble with path pattern 'scripts/.' which was not working as 'included-region'. The reason was that I did enable the *'shallow clone' option in git scm settings. When the option 'shallow clone' was disabled the 'included-region' parameter worked as expected. Thanks to Mark Waite for sharing the Jenkins job config.xml which helped me to detect differences with job.

Add Comment

[kanthak@freenet.de (JIRA)]

Christian Kanthak edited a comment on JENKINS-22457

Re: Git push will trigger a build even though no path matches included regions

Just a note for others visiting this page because they have problems with 'included-regions' as I had:

I also had trouble with path pattern 'scripts/.*' which was not working as 'included-region'. The reason was that I did enable the *'shallow clone'* option in git scm settings. When the option *'shallow clone'* was *disabled* the 'included-region' parameter worked as expected. Thanks to [~markewaite] for sharing the Jenkins job config.xml which helped me to detect differences with my job.

Add Comment