Closed Bug 1413141 Opened 8 years ago Closed 8 years ago

Prepare Jenkins instances for using email-ext plugin in pipelines

Categories

(Cloud Services :: FXTest-infra, enhancement)

Product:
Cloud Services
Component:
FXTest-infra
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: davehunt, Assigned: oremj)

Details

We'd like to switch to the email-ext plugin [1] for build notifications. This will allow us to include failure summaries and to attach the build log and reports. We need to ensure we have the plugin installed and configured on the following instances: * fx-test-jenkins.stage.mozaws.net * qa-master.fxtest.jenkins.stage.mozaws.net On these instances, please: * Install the latest version of the plugin [1] * Configure the following in Manage Jenkins > Configure System > Extended E-mail Notification * Default Recipients: fte-ci@mozilla.com * Reply To List: firefox-test-engineering@mozilla.com Once this is done we can merge https://github.com/mozilla/fxapom/pull/156 and start working on switching the remaining pipelines to the improved build notification emails. [1] https://plugins.jenkins.io/email-ext
oremj: Does your team monitor this product/component, or should we assign/needinfo when we create bugs that require your assistance?
Flags: needinfo?(oremj)
needinfo is always best for me. Assigning also works. When would you like us to do this?
Flags: needinfo?(dave.hunt)
oremj: As soon as is convenient. Unless the plugin is not installed (I suspect it is) then there will be no need for a restart.
Assignee: nobody → oremj
Flags: needinfo?(dave.hunt)
email-ext is pinned 2.57.2 in enterprise Jenkins, so I didn't upgrade the plugin on either instance. I did configure default recipients and reply to list.
Flags: needinfo?(oremj)
Thanks Jeremy!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.