I have Hudson set up with a large number of jobs, one per stream in my AccuRev
stream hierarchy. If I check in or promote a documentation change to any stream,
it will trigger Hudson to execute builds against that stream and all lower level
(child / development) streams that the documentation change flows down to. I
want this build behavior for code changes, but not for documentation updates. I
don't see any way to allow for this in Hudson, and Hudson seems to ignore the
AccuRev include/exclude rules set up on my lower-level development streams that
exclude the documentation directories.