[users at bb.net] notification by status changes per branch

[Pierre Tardy]

Hi Gelonida,

It looks like your requirements are pretty specific, but guess what?
Buildbot is written in python, and you can very easily subclass the mail
reporter, and make it suite your needs.
Have you looked at how the mail reporter is written?
I would start by looking at this method:
https://github.com/buildbot/buildbot/blob/master/master/buildbot/reporters/mail.py#L295
and the associated test (to debug your algorithm)
https://github.com/buildbot/buildbot/blob/master/master/buildbot/test/unit/test_reporters_mail.py#L420

You can even create several mail reporters for different use cases, and
potencially with different email templates.

Pierre



Le sam. 11 mars 2017 à 13:10, Gelonida <gelonida at gmail.com> a écrit :

> Hi,
>
>
> Context:
> -------------
>
> I just started with buildbot 9 (and have a little experience with
> buildbot 8)
>
> In our environment we have about 50 different git repositories and about
> 100 builders (between 1 and 4 builders per repo).
>
> Each repository has up to 20 branches which can be grouped into
> production branches, integration branches and developer branches.
>
>
> Problem:
> ----------------
>
> I'd like create notifications whenever:
>
> - a given branch changes it's build status
> - a build has been performed on a new branch
>
>
> Question(s):
> ------------------
>
> I was reading through the documentation of the reporters and I saw,
> that  MailNotifier has a 'mode' attribute which I could set to 'change'.
> However if I understand correctly I would not achieve what I wanted.
> If I have a 'passing' branch and a 'failing' branch and developers would
> push commits in turns then I would get notified on every change.
>
>
> Is there any such functionality available? If yes, where can I get more
> information?
> Does anybody else have a similar issue? If yes, how do you deal with it?
>
> If this is not available. Do you have any advice of how I could
> implement this within buildbot with a self written Reporter (plugin),
> which had to be able to remember/access the most recent build status for
> each branch.
>
> I thought alternatively about an HTTP push notification to another self
> written server who is then dealing with the notifications but this might
> be overkill.
> However I wonder how stable this would be if a notification got lost due
> to network issues. I assume, that a 'timed-out' notification will not be
> resent at a later time.
>
>
> Thanks a lot in advance for any ideas / feed back
>
>
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20170312/828a9990/attachment.html>