I downloaded svn-notify (readily available on the net for *nix or windows) a little while ago and am trying to configure it now. It comes with basic pre- and post-commit hooks which I am now customizing to fit my needs, and looks like it will provide all of the functionality I am requiring as of now. I may go with more Trac integration at a later date, but for now all I desire is the email notification.
Brett On May 9, 3:45 pm, [EMAIL PROTECTED] wrote: > On May 9, 2:19 pm, Brett <[EMAIL PROTECTED]> wrote: > > > Manu-- > > > Thank you for yuor help! I am not much of a Python programmer ... do > > you know of any resource I can use to have a post-commit hook to > > merely send a notification email out to a group of people with the > > changeset number, who committed the changeset, a list of the files > > changed, and the contents of the log entry? > > > I really don't need the features to close tickets and add changeset > > logs to tickets at this current point in time. > > > Of course, if this is independent of Trac (which I get the sense it > > might be) ... please let me know and I will look elsewhere. > > > Thanks again for your help! > > > Brett > > <snip> > > I think you have 2 avenues here. You can do it purely as a subversion > post-commit-hook (helps if you have a pre-commit-hook to enforce all > the things you are asking for), or you can have a subversion post- > commit-hook, which calls a trac-post-commit-hook, which updates the > tickets, and configure trac to notify people of changes to the > ticket. (possibly customizing this to include the information if they > don't want to navigate to the web page to READ it (say, one of the > recipients is another script :D) > > Anyway, trac can be configured to notify people of a change to the > ticket, and subversion can be configured to update a ticket in trac, > so this is possible the simplest route if you ultimately want to do > more with trac and the commit. The shortest immediate route, is > likely to have a Subversion post-commit-hook script, which fires off > the email with the information you want, which all comes from > subversion, maybe via smtp for example. Keep in mind all the calls to > Subversion you make to collect the information, would still be called > whether or not you do anything via trac. Now, sending the actual > email can be a pain either way on windows, depending on your setup :D > > ok, to summarize: > > all the information can get pulled from Subversion as a Subversion > post commit hook. > It can then either be sent to trac, to update a/several ticket(s) or > can be directly mailed to the recipients. (Trac can Also pull it from > subversion, but that a symantic) > If sent to Trac, Trac can be configured to update the ticket(s), > separately, it can additionally be configured to notify recipients on > change to a ticket. > > Finally, I am a trac noob, so I'd love to hear the other options (I am > sure there is a webdav route, maybe a DB trigger route...etc.) > > :D --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
