On Wed, 7 Dec 2005, Phillip J. Eby wrote:
At 12:51 PM 12/7/2005 -0800, Andi Vajda wrote:
On Wed, 7 Dec 2005, Mike Taylor wrote:
Ok, let me try and summarize so we can focus on what is needed to solve
the different issues raised:
- we need to add email notifications to the tinderbox build/test failed
event
- we need to add SVN commit information to the tinderbox status page and
notifications
- we need to make it easy to either extract or locate the actual point of
failure or error inside the build logs
Did I miss anything?
- we need to eliminate false positives so that tinderboxes don't
discredit
themselves.
Could you be more specific? I'm not sure what you mean here.
Currently, the tinderboxes go red quite often for no good (or obvious) reason.
If they then cry wolf, people will learn to ignore them.
- we need to automate locking down the svn tree and give people who need
it
a convenient way to override the lock down so that they can resolve the
problem.
+1. I think this should eventually extend to also rejecting commits to trees
with current build failures, unless you include a valid "failure number" in
the commit message. This would stop accidental commits to burning trees.
+1 !
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
