Hello, jekins is currently spamming digikamdevel, when every commit is made. And the message is generated when build is unstable, not when it fails. It is not going to be stable anytime soon, so better configure it to send a message only when build fails.
I can do nothing for a few days as I am traveling back to US from akademy. I will try to sort out per project notificaton verbosity. Scarlett
On Sat, Aug 1, 2015 at 10:10 AM, Veaceslav Munteanu <[hidden email]> wrote:Hello, jekins is currently spamming digikamdevel, when every commit is made. And the message is generated when build is unstable, not when it fails. It is not going to be stable anytime soon, so better configure it to send a message only when build fails.For any jenkins related messags, always please CC sgclark(at)kubuntu.orgor bcooksley(at)kde.orgNevertheless, wouldn't it make more sense to make the build stablerather than disabling the "police" altogether? If it's unstable becauseof tests not passing because of some missing code, then disable thosetests as they are useless anyway for the time being. Cheers-- Martin Klapetek | KDE Developer
Locked
