michaelsembwever commented on a change in pull request #10: Configure so emails 
are sent when a build fails…
URL: https://github.com/apache/cassandra-builds/pull/10#discussion_r320936973
 
 

 ##########
 File path: jenkins-dsl/cassandra_job_dsl_seed.groovy
 ##########
 @@ -105,6 +105,19 @@ job('Cassandra-template-artifacts') {
             javadocDir 'build/javadoc'
             keepAll false
         }
+        extendedEmail {
+            recipientList('bui...@cassandra.apache.org')
+            triggers {
+                stillUnstable {
 
 Review comment:
   Fixed.
   
   > These triggers would send on every build failure - there is an alternate 
firstFailure{} trigger, so only one email would be sent in the case of repeated 
build failures.
   
   Let's start with `failure {}`, as no one should be committing on top of a 
broken HEAD. (In a perfect world, that should be as bad as breaking it to begin 
with.)
   (If/When we change to `firstFailure{}` then `culprits()` looks like it can 
be removed.)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to