Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Core maintainers should be notified when a branch test for an environment is failing - with a diff against the previous nights results.
The initial notification list should be:
xjm, effulgentsia, webchick, catch, alexpott
For MVP, this can be configured directly in Jenkins if necessary.
In the long term, it would be ideal if notification settings were configurable on D.O.
Comments
Comment #1
hestenetComment #2
hestenetThis has largely been blocked by splitting the Jenkins jobs and making sure D.O can keep track of child jobs/builds.
@Drumm has essentially resolved those issues at this point so we should hopefully be able to implement basic notification in Jenkins shortly.
The long term goal is still notifications configurable on D.O and/or notification list passed as a parameter into DCI
Comment #3
basic CreditAttribution: basic at Drupal Association commentedI've added notifications to Project php5.5 mysql5.5 Simpletest Runner to send any time there is a failure or change in state (i.e. failure -> success). Are there other branch tests that I should add xjm, effulgentsia, webchick, catch, alexpott to?
Comment #4
basic CreditAttribution: basic at Drupal Association commentedComment #5
David_Rothstein CreditAttribution: David_Rothstein as a volunteer commentedAssuming we turn this on for Drupal 7 core, please add me to the list.
I'd actually be happy to find someone else to get these emails, but for now I think it's me :)
Comment #6
webchickMoving this from a 8.0.0-RC1 blocker to a "Shut off PIFT" blocker, per conversation with @xjm, @catch, @alexpott, and @effulgentsia yesterday.
We should probably discuss if we even want to make it block that, since there is a workaround: just manually refresh a page like https://www.drupal.org/pift-ci-job/23491, which contains the historic results to help indicate when a regression may have been committed.
Comment #7
hestenetComment #8
drummComment #11
drummComment #13
drummThis can be deployed now.
Comment #14
drummThis is now deployed.