Hi, Simon Josefsson <[email protected]> writes:
> I can think of several things to improve notification quality: 1) make > sure that only one e-mail is sent if builds stop working -- only ever > send another e-mail if one build has succeeded since the last failure. Currently, what Hydra does it sends an email each time a build fails; and it tries to build each time one of the inputs changed. So, for instance, if an Inetutils build fails, then Hydra won’t trigger a new build until either the Inetutils repo, or the Gnulib repo, or the standard Nix build environment change. > 2) delay sending e-mail a few hours to see if the problem persists. > Sometimes you check in something that is clearly broken and you fix it > minutes later yourself, and getting a notification for that seems > useless. I don’t develop Hydra myself, but I could discuss such changes with those involved. > Do you have a pointer to how these e-mails looks like? It looks like this: --8<---------------cut here---------------start------------->8--- Hi, This is to let you know that Hydra build 182029 of job nixpkgs:stdenv:gcj has FAILED. Complete build information can be found on this page: http://hydra.nixos.org/build/182029 A summary of the build information follows: Build ID: | 182029 Nix name: | gcj-wrapper-4.4.2 Short description: | GNU Compiler Collection, version 4.4.2 (wrapper script) Maintainer(s): | Ludovic Courtès <[email protected]> System: | x86_64-linux Derivation store path: | /nix/store/ha7aski4k7k0fn3ikpq0fpqgildqvisb-gcj-wrapper-4.4.2.drv Output store path: | /nix/store/2p54n3im7yv1bl8gn3k79qbk1rp73cg9-gcj-wrapper-4.4.2 Time added: | 2009-12-10 15:59:50 Build started: | 2009-12-10 15:58:50 Build finished: | 2009-12-10 15:59:50 Duration: | 60s The build inputs were: Name | Type | Value --------+--------+---------------------------------------------------------------------- nixpkgs | svn | https://svn.nixos.org/repos/nix/nixpkgs/branches/stdenv-updates:18879 system | string | x86_64-linux Regards, The Hydra build daemon. --8<---------------cut here---------------end--------------->8--- Thanks, Ludo’.
