Stepan Mishura wrote:
On 3/19/08, Oliver Deakin <[EMAIL PROTECTED]> wrote:
Hi Stepan,
Thanks for fixing that! I did do a build on Linux at the time, but it
was a sequential build from an already existing workspace so it must
have missed that change somehow. Ill build from scratch next time to
make sure!
I do watch the alerts list, and I fixed the build break I saw (the one
you raised initially), but received no further mails indicating a break
on Linux x86. I take it a mail only gets sent when the state of the
build changes? So if there is a second break (as in this case) no mail
is sent because the build state does not change?
Yes, it is. If the build is broken than only initial notification is
sent, no repeated notifications are sent.
It is expected that once committers see a notification about build
breakage all commits are stopped and everybody wait when the build is
fixed and notification about build recovery is received - I think
everybody should know that if the build is broken no tests are run. We
tried to establish a practice with stopping commits but it seems that
people don't like to follow it :-)
Like you say, if somebody breaks the build (via the alert notifications
etc.) then it is their duty to fix it (i.e. see the successful message).
It's pretty simple.
Regards,
Tim
