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