[dev] [commits] Horde branch master updated. 52fa2008c9e81d5337cdb957ac9a8d4c0e442c2a

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

> commit d4ed33b6498fb20241f587b00cba7d450b987a6f
> Author: Jan Schneider <jan at horde.org>
> Date:   Tue Jun 4 12:27:11 2013 +0200
>
>     Tweak build notifications.
>
>     Send IRC notifications too, and only send failure notifications  
> when breaking
>     the build for the first time.
>
>  .travis.yml |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
>
> http://git.horde.org/horde-git/-/commit/d4ed33b6498fb20241f587b00cba7d450b987a6f

This doesn't seem correct.  Example:

1. Dev commits.  The commit is fine but the build breaks because of  
network issues/DB issues on Travis.  Dev checks failure notification  
and dismisses since there is nothing wrong with actual commit.
2. Dev commits broken code.  Dev never gets notification that the  
commit is broken (unless they manually go to travis status output  
webpage) since this is not the "first" broken commit, even though it  
is the first broken commit from the perspective of code  
quality/correctness.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]