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

hestenet’s picture

hestenet
He/Him
Location Portland, OR 🇺🇸
commented
Parent issue: » #2467925: [plan] Remove blockers to the "minimum viable" state of DrupalCI to ship Drupal 8 RC1
hestenet’s picture

hestenet
He/Him
Location Portland, OR 🇺🇸
commented

This 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

basic’s picture

basic commented

I'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?

basic’s picture

basic commented
Assigned: Unassigned » basic
Status: Active » Needs review
David_Rothstein’s picture

David_Rothstein commented

Assuming 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 :)

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Parent issue: #2467925: [plan] Remove blockers to the "minimum viable" state of DrupalCI to ship Drupal 8 RC1 » #2534132: Disable Legacy Testbots and use drupalCI as our testing infrastructure

Moving 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.

hestenet’s picture

hestenet
He/Him
Location Portland, OR 🇺🇸
commented
Related issues: +#2538160: Add email notifications
drumm’s picture

drumm
he/him
Location NY, US
commented
Title: Notify core maintainers of test failures with a diff against the previous nights result » Notify core maintainers (and anyone who wants to subscribe) of test failures (for a branch & environment) with a diff against the previous nights result
Project: DrupalCI: Dispatcher (Modernizing Testbot Initiative) » Project issue file test
Version: » 7.x-3.x-dev
Assigned: basic » drumm
Status: Needs review » Active

  • drumm committed 4197790 on 7.x-3.x 
    Issue #2518026: Start with non-pass or all for all notifications

  • drumm committed 4197790 on 7.x-3.x 
    Issue #2518026: Start with non-pass or all for all notifications
  • drumm committed fe1d9b1 on 
    Issue #2518026: Add branch & environment notifications
drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Needs review

  • drumm committed d962d0e on 7.x-3.x 
    Issue #2518026: Branch notifications - only query for them on branch...
  • drumm committed fe1d9b1 on 7.x-3.x
    Issue #2518026: Add branch & environment notifications
drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Needs review » Fixed
Issue tags: +needs drupal.org deployment

This can be deployed now.

drumm’s picture

drumm
he/him
Location NY, US
commented
Issue tags: -needs drupal.org deployment

This is now deployed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.