RE: [wtp-dev] How many of you have been reading the wtp-releng buildnoti

["Ted Bashor" <tbashor@xxxxxxx>]

Alternatively, don't send out any mail for a consecutive successful
build.

 

I think it's worthwhile to spam everyone on a failed build - generates
peer pressure to get it fixed.  But we don't need to know when things
are chugging along fine.

 

A system for addressing build breakage mail to individual committers
sounds like a good idea.

 

-Ted

 

________________________________

From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Monday, September 11, 2006 8:22 PM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] How many of you have been reading the wtp-releng
buildnotice results? 

 


I know, I know ... not many of you :) 


As we discussed,
http://wiki.eclipse.org/index.php?title=Team_thoughts_on_continuous_impr
ovement 
and as has been requested,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=152277 

our continuous build process swamps mailing lists with too many notices
to be useful. 

I propose 
        1. we turn off mailing list notifications 
        2. allow people to subscribe to RSS feed (see the rss button on
http://build.eclipse.org:7777/cruisecontrol/) 
             if they would like to get/see notice of each build. 
        3. And, we use cruiseControl's built-in notification mechanism
to send "personal" mail to committers: 
                A. It would require we put committers cvs user IDs, and
their email address in the CVSROOT/users file. 
                     (so, some risk of "mail address mining", but, IMHO,
minor or unavoidable problem). 
                B. If someone releases to build, they will be notified
with mail once that build is successful, such as example 
                     messages below. (if they didn't release, they won't
get mail, unless it fails ... 
                C. If a build fails, then all committers will be
notified with mail, similar to example below. 
        4. the "wtp-releng" list would still be used to communicate
smoke tests, build schedules, status, and general 
             "releng" topics, just not each build result. 


What do you think? Any other suggestions? Objections? 


If you would like your userid/mail address put in CVSROOT/users file,
please post it to 
bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=152277 
That is, this will be an "opt in" list ... if anyone really doesn't want
their ID and mail address there, we won't require it! 
But, it will be for committers only ... others will have to use the RSS
feed if they want to know about each build, similar to 
mailing list..(Note: these ids and mail addresses eventually go to the
webmaster to put in 'users' file ... the "masters" turned off my 
access to it once they found I could monkey around with it :) [it wasn't
really me ... but we were the only project with access there 
for a while]. 

Note: there is one possible side effect ... while its opt-in for
"normal" email addresses ... 
the default behavior is to address the email to cvs_userid@xxxxxxxxxxx.
(the build machine's "host" address). 
So, I don't know how many of you use an 'eclipse.org' mail address ...
but ... 
if you do, then that address will get these notices, if you do not
opt-in with another address. 

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = 
[wtp-R2.0-I-build] wtp-R2.0-I Build Failed 

View results here ->
http://build.eclipse.org:7777/cruisecontrol/buildresults/wtp-R2.0-I?log=
log20060911204404 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = 
[wtp-R1.5-M-build] wtp-R1.5-M build.138 Build Successful 

View results here ->
http://build.eclipse.org:7777/cruisecontrol/buildresults/wtp-R1.5-M?log=
log20060911144118Lbuild.138 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = 

>>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.