20 Dec
2012
20 Dec
'12
12:03 a.m.
On 12/19/2012 05:25 PM, Marius Dumitru Florea wrote:
On Wed, Dec 19, 2012 at 4:21 PM, Vincent Massol
<vincent(a)massol.net> wrote:
And it currently doesn't work, it's printed literally.
Hi devs,
I'm working on configuring jenkins email configuration for all jobs (I'm
scripting it).
We need to agree on the mail sending strategy.
Here's what I propose:
* We send mail to the list when there's a
build failure
* We send mail to the list when the build is fixed
+1
* We send a special mail with a different subject
to committers/culprits when there's a build failure (this is the "You broke the
build! Fix it now!" email that is currently sent by platform)
* We send a special mail with yet a different subject to committers/culprits when
there's a second build failure (this is the "Hurry up! The build is still failing
because of you! Stop whatever you're doing and fix it!" email that is currently
sent by platform)
+0.5
In addition I propose the following content:
"
Check console output at $BUILD_URL to view the results.
Failed tests:
${FAILED_TESTS}
Last build logs:
${BUILD_LOG, ".*Finished at:.*", 100, 100, 0, true, null, false, null, true}
"
(this last line means to include the 100 lines around the "Finished at" message
in the log).
+1
--
Sergiu Dumitriu
http://purl.org/net/sergiu