Sorry I wasn't clear. The issue is that the build doesn't run if excluded regions are set.

Suppose you've the hierarchy

file.c
dir1/
dir1/file1.c
dir2/
dir2/file2.c
...

With version 1.6 of the CVS plugin, one could set an excluded region of "[^/]*.c". Then changes to "file.c" would (correctly!) not trigger a build, but changes to "dir1/file1.c" would trigger a build. Now, neither triggers a build.


I'm not sure how useful the job config would be. Because of this bug, we had to remove the excluded regions (at the cost of a large increase in spurious builds) in order to get the builds we needed, due to changes in subdirectories.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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/groups/opt_out.
 
 

Reply via email to