I use subversion as a version control system. I have configured subversion to notify Jenkins when a commit takes place by using a post-commit hook. This has made it possible to use very infrequent SCM polling interval for those projects that are triggered by SCM changes.
Infrequent polling has a drawback. Changes that are committed while Jenkins is down are not noticed until polling founds them or a new commit brings them into a view.
It would be nice to be able to instruct all projects that are triggered by SCM changes to poll for changes once Jenkins is started. The idea is to build only those projects for which polling found some changes to avoid unnecessary load. This would also leave out projects that have other triggering means, like those that are built periodically regardless of changes.
Do you see if this feature would fit in the scope of this plugin?