Notification » History » Version 1

Version 1/3 - Next » - Current version
Marc Mengel, 02/05/2014 10:50 AM


New issues notification

For new issues, there is a "Newissuealerts" plugin installed, you can turn it on in your Settings/Modules box for your project, and then use the Settings/"Email on New Issue" page to configure email addresses to get notified of new issues.

Commit/push messages

For commit/push messages, you need to update the hooks directory in the repositories, by ssh-ing into the account
and editing it (you need to be a Manager on the project, and be using Kerberos authentication to do this).

We do have some scripts that will use the RepositoryMailinglists field on yor Settings/Information page; or you can roll your own, there is an executable
/usr/local/bin/get_rm_ml projectname
which will pull that text for you to use in your scripts.

I've been planning at some point to do a Grand Unified notification script
that would handle CVS, Git and Subversion notifications; but it's been
idling on a back burner for some time.

for Git, we also have several flavors of git_commit_notifier lying around one which pulls the malinglist config stuff out of the repository, and the other which uses the get_rm_ml business. You can make a symlink
post-receive -> /fnal/ups/db/fnal_git_notifier/current/scripts/fnal-git-notify-redmine
for the git_commit_notifier that gets the mailinglist text block into its configuration, or you can put in
post-receive -> /fnal/ups/db/fnal_git_notifier/current/scripts/fnal-git-notify-redmine
for the one that gets things from the repository.

For SVN we have /usr/local/bin/ which some people like for
sending fancy commit messages.