Brett Porter wrote:
So... not much response on this.
We separated notifications from commits because of the theory that some
non-committers might want the commits and not the notifications, and I
could understand that some committers might monitor SVN via things other
than the list so would only be on notifications.
But notifications seems compulsory for committers. WDYT?
Yes, sure.
We definitely need to improve the technology behind it too to reduce the
noise and more accurately identify who caused a problem so they can
think to fix it.
That's a must. I currently filter notifications to a separate mailbox
which I rarely look at. The reason being that I don't understand the
messages that get sent there.
It's easy to get confused by the titles when the products being checked
out and built are themselves software that can check things out and
build stuff. Here are a couple of examples:
[continuum] BUILD <result>: <product>
[continuum build trunk - <result> - <command>] <date>
[maven2 build trunk|branches/maven-2.0.x - <result> - <command>] <date>
[surefire jdk1.3 build trunk - <result> - <command>] <date>
As for the <result> above SUCCESS|SUCCESSFUL sounds good and
FAILURE|FAILED sounds bad. I got that covered :) but what about the rest?
- Brett
On 3/08/2006 3:09 PM, Brett Porter wrote:
It seems that build failures are going unnoticed recently. And for
once, I'm not the one causing them (except that MRM webapp - doh!)
a) is everyone subscribed?
b) is everyone paying attention when they fail?
c) what can we do to make it better? (yes, getting everything into
Continuum is one thing)
- Brett
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
