Not yet On 11/28/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
it is getting spam-like.... Doesn't CC already do the "send no mail until state change"?
Not yet. OK. I'll stop CC while this feature will be implemented. geir
Vladimir Ivanov wrote: > Should I stop the CC while the issue with test compilation will be > resolved? > > Vladimir > > On 11/28/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: >> >> >> >> Tim Ellison wrote: >> > Vladimir Ivanov wrote: >> >> On 11/28/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: >> >>> I've seen a few of these repeated - shouldn't the CI system not send >> the >> >>> same message over and over? >> >> Now the system sends notification for each failure. It can de changed >> to >> >> send notification only for first failure but such system will be >> useless in >> >> the time of failure investigation. >> >> >> >> The current scenario based on the assumption that each failure is >> critical >> >> and should be fixed ASAP or patch should be reverted. In this case >> next >> CC >> >> cycle will pass. >> >> >> >> Should I change the CC to send one notification for build failure? >> > >> > I would say so, otherwise we become blind to the repeated messages. >> > Once the build break flag goes up people should turn their attention to >> > it until it is resolved. >> >> Exactly. I now that I'm getting a bit jaded from the repeated stream. >> >> One message, and then stop. When the CI build/test run finally works >> again, then another message saying "BUILD FIXED" (or whatever). >> >> geir >> >> >
