github.com/justinjmoses/evergreen@v0.0.0-20170530173719-1d50e381ff0d/config_prod/mci-notifications.yml (about)

     1  #####################################################
     2  #       MCI Notifications Configuration File        #
     3  #####################################################
     4  #                                                   #
     5  # This is the configuration file for MCI email      #
     6  # notifications.                                    # 
     7  # It primarily consists of notifications and teams  #
     8  # subscribed to any number of such notifications.   #
     9  #                                                   #
    10  #####################################################
    11  
    12  
    13  #####################################################
    14  #                      README                       #
    15  #####################################################
    16  #                                                   #
    17  # By default, notifications on build success and    #
    18  # build failure are sent to the blamelist for that  #
    19  # build - which consists of all those who made a    #
    20  # commit between the time the last activated build  #
    21  # was pulled by MCI and the current build on which  #
    22  # the notification is triggered for.                #
    23  #                                                   #
    24  # Recipients for each notification are optional -   #
    25  # the typical way to get notified on any event is   #
    26  # to subscribe to it as part of a team.             #
    27  #                                                   #
    28  # Teams can subscribe to as many notifications as   #
    29  # they wish. They can also specify whether want     # 
    30  # logs to be included as part of the notifications  #
    31  # (note that this is only useful for task failure   #
    32  # notifications). In addition team notifications    #
    33  # are specified per project.                        #
    34  #                                                   #
    35  # If however, an interested party is not part of a  #
    36  # team but wishes to receive one or more notifica-  #
    37  # tions, the person can just add their email        #
    38  # address to the notification's recipients list.    #
    39  # This will ensure that they equally get notified   #
    40  # accordingly.                                      #
    41  #                                                   #
    42  #####################################################
    43  
    44  
    45  
    46  #####################################################
    47  #                   Notifications                   #
    48  #####################################################
    49  
    50  notifications:
    51  - name: build_failure
    52    project: mongodb-mongo-master
    53    recipients:
    54  - name: build_success
    55    project: mongodb-mongo-master
    56    recipients:
    57    skip_variants:
    58  - name: build_success_to_failure
    59    project: mongodb-mongo-master
    60    recipients:
    61    skip_variants:
    62  - name: task_failure
    63    project: mongodb-mongo-master
    64    recipients:
    65    skip_variants:
    66  - name: task_success
    67    project: mongodb-mongo-master
    68    recipients:
    69    skip_variants:
    70  - name: task_success_to_failure
    71    project: mongodb-mongo-master
    72    recipients:
    73    skip_variants:
    74  - name: task_completion
    75    project: mongodb-mongo-master
    76    recipients:
    77    skip_variants:
    78  - name: build_completion
    79    project: mongodb-mongo-master
    80    recipients:
    81    skip_variants:
    82  
    83  #####################################################
    84  #                     Teams                         #
    85  #####################################################
    86  
    87  teams:
    88  - name: Kernel Team
    89    address: kernel@10gen.com
    90    subscriptions:
    91    - project: mongodb-mongo-master
    92      notify_on: 
    93      skip_variants:
    94  - name: Kernel Tools Team
    95    address: mci@10gen.com
    96    subscriptions:
    97    - project: mongodb-mongo-master
    98      notify_on:
    99      - task_success_to_failure
   100      skip_variants:
   101    - project: mongodb-mongo-v2.6
   102      notify_on:
   103      - task_success_to_failure
   104      skip_variants:
   105    - project: mci
   106      notify_on:
   107      - task_success_to_failure
   108      skip_variants:
   109  - name: MCI Alerts
   110    address: mci-alerts@10gen.com
   111    subscriptions:
   112    - project: mongodb-mongo-master
   113      notify_on:
   114      - task_success_to_failure
   115      skip_variants:
   116    - project: mongodb-mongo-v2.6
   117      notify_on:
   118      - task_success_to_failure
   119      skip_variants:
   120  - name: Pager Duty
   121    address: mci-failure@mongodb-kernel.pagerduty.com
   122    subscriptions:
   123    - project: mongodb-mongo-master
   124      notify_on:
   125      - task_success_to_failure
   126      skip_variants:
   127    - project: mongodb-mongo-v2.6
   128      notify_on:
   129      - task_success_to_failure
   130      skip_variants:
   131  
   132  
   133  #####################################################
   134  #                    Patches                        #
   135  #####################################################
   136  patch_notifications:
   137  - project: mongodb-mongo-master
   138    notify_on:
   139      - task_failure
   140    skip_variants:
   141  - project: mongodb-mongo-v2.6
   142    notify_on:
   143      - task_failure
   144    skip_variants: