Re: Programming a Watcher File

The idea is to allow users to specify exactly which they want to
watch. It might be a few configuration files, images, etc.

Hudson will notify if any files in the entire project are changed, and
when you do a dozen builds each day, the developers start to ignore
these build notices.

This is something that most other version control systems allow and is
usually built in. Third party clients like SVN Notifier and Commit
Notifier is that they must be user installed and running on the user's
machine. If you aren't on that machine, you don't get notified.

Something like Fisheye is good because that allows users to set
notifications and is not dependent upon the user's own system.
However, we don't have Fisheye.

Subversion comes with a post-commit notification script written in
Perl, but this script requires a configuration file that sits on the
server. That means developers have to ask the administrator to set and
change notifications. By putting the notification configurations
inside the repository, I allow users to set their own notifications.
Since it is the server that's running it, the notifications aren't
machine dependent.

-- 
David Weintraub
qazwart_at_gmail.com