Hi Mojca, What I do to group those kind of reporting is to have a parent build, and use the triggereable scheduler.
You can then put the reporter on the parent build only, and build a summary email with everything that broke. On eight however, It is difficult to get a reference for triggerered builds. so that might not be the best help for you. Your idea of the extraHeaders looks good to me, and sounds like a good addition. We would have to make sure we find a correct header that we can use, and works well for most email clients that can group emails into conversations. Pierre Le mer. 12 oct. 2016 à 10:19, Mojca Miklavec <[email protected]> a écrit : > Hello, > > Most often a "broken commit" (or known-to-be-incompatible software) > breaks functionality on multiple (or all) slaves. > > So we would find it super useful if we could group failure emails from > different slaves by SVN revision. > > We planned to add an additional header like > In-Reply-To = [email protected] > > I see that MailNotifier supports adding > extraHeaders=... > but it's not clear to me how to access the svn revision or git shasum > at the point where MailNotifier is being added. > > I would be grateful for ideas about how to properly implement that (in > version eight). > > The next thing we would want to do is to group forced builds (when > someone triggers a build from the web interface to all slaves, we > would need some similar unique identifier to be able to add the same > In-Reply-To to all failure emails). > > Thank you, > Mojca > _______________________________________________ > users mailing list > [email protected] > https://lists.buildbot.net/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
