You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/12/24 01:15:00 UTC
[jira] [Resolved] (IMPALA-4832) Set up email notifications for
jenkins.impala.io
[ https://issues.apache.org/jira/browse/IMPALA-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-4832.
-----------------------------------
Fix Version/s: Not Applicable
Resolution: Won't Fix
jenkins.impala.io now comments on Gerrit reviews. We can open a new issue if this is still an issue.
> Set up email notifications for jenkins.impala.io
> ------------------------------------------------
>
> Key: IMPALA-4832
> URL: https://issues.apache.org/jira/browse/IMPALA-4832
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 2.9.0
> Reporter: Lars Volker
> Assignee: Laszlo Gaal
> Priority: Minor
> Labels: asf, jenkins
> Fix For: Not Applicable
>
>
> We may want to set up email notifications for the new jenkins.impala.io instance. To do so we could use the [Amazon Simple Email Service (SES)|https://aws.amazon.com/ses/]. However this will require to have a validated email address to send the emails from.
> We could ask the ASF for something like jenkins@impala.apache.org. If that does not work, we might also consider using an @cloudera.com address, since Cloudera currently provides and administers the infrastructure. As yet another alternative, we might try to find a way to receive emails for jenkins@impala.io and use that one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)