On 20.04.2015 03:26 AM, Felipe Sateler wrote: > Travis by default only sends mails on broken builds, and the first > successful built after a broken one. I have only experience with Jenkins, and concerning this feature, both system sound about equal. With Jenkins, it's one mail per build job type and that can get quite nasty if having multiple build jobs for multiple distros for multiple architectures. > Moreover, travis does not try > every commit, but only push commits. So volume should not be an issue. > Is there any reason you think this would be a bad idea? I think it's an issue exactly because of the (potential) volume, the message sizes (if [truncated] build logs are attached) and the general lack of being useful for users/discussions. The -commits mailing list sounds like a more appropriate place for this sort of auto-generated information. Despite for developers working on PA directly, those messages will mostly be needless spam. Mihai -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 884 bytes Desc: OpenPGP digital signature URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20150420/a3892ce9/attachment.sig>
