The subcomponent for this enhancement should really be SCM, but I didn't see
that option :/

Please note:
The enhancement below is best suited for "Latest" type builds. That is, builds
that are run to make sure that when a projected is checked out from an SCM that
it will always result in a SUCCESSFUL build.

Description:
Please see http://www.nabble.com/Excludes-List-tf4488311.html#a12855652 for full
description.

"Better SCM polling support that doesn't trigger a build for changes in certain
regions"

On a Job by Job level, have an "Excludes List/Region" under the "Build Triggers"
that would specify files/folders that are irrelevant from the build's status
(success or failure).

For instance if you are running an apache webserver and have virtual-host
definitions that redirect static content to a folder outside the application
war/ear file, all static content becomes irrelevant to the status of a build,
thus Hudson should not have to build the job if the only thing that has been
updated in the SCM is static content.

Another example is *.sql scripts. If your build process does not automatically
run these scripts, then they become irrelevant to the build's status (success or
failure). If one of these *.sql scripts is modified, it will not effect the
build directly, thus Hudson should not schedule and run a build for it.

This would save Hudson from having to schedule builds that will always succeed.