flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Metzger <rmetz...@apache.org>
Subject Re: Master not building and how to notice it faster in the future
Date Thu, 12 Feb 2015 14:07:14 GMT
No, I think this won't work because travis only sends emails to accounts
associated with the repository. In this case its the apache/flink github
repository and nobody of us is actually part of the organization.

See http://docs.travis-ci.com/user/notifications/:

> The most common cause for not receiving build notifications, beyond not
> having a user account on Travis CI, is the use of an email address that's
> not registered and verified on GitHub. See above on how to change the email
> address to one that's registered or make sure to add the email address used
> in this repository to your verified email addresses on GitHub.


I don't know if we can verify our dev list with travis/github. And if, I
don't know if the mailinglists support HTML mails.


On Thu, Feb 12, 2015 at 3:03 PM, Ufuk Celebi <uce@apache.org> wrote:

> I just found out that we can simply activate email notifications for build
> failures.
>
> Can we allow build@travis-ci.org to send to dev@f.a.o?
>
> On Wed, Jan 21, 2015 at 9:41 PM, Robert Metzger <rmetzger@apache.org>
> wrote:
>
> > I'm actually quite happy with the travis setup. Since most of the
> > contributors/committers have travis activated for their forks, its very
> > convenient to run tests on travis, without polluting any public apache
> > infrastructure.
> > Also, it would add another big dependency to a (perceived) unstable
> apache
> > infrastructure.
> > Lastly, I don't know if anybody has time right now to migrate away.
> >
> > I think hacking a little REST2Mail service in Java for the Google Cloud
> is
> > a nice task for some wellness-programming on the weekend.
> >
> > On Wed, Jan 21, 2015 at 9:29 PM, Henry Saputra <henry.saputra@gmail.com>
> > wrote:
> >
> > > Would it be better to use Github Jenkins plugin [1] to connect to ASF
> > > Jenkins cluster?
> > >
> > > [1]
> > >
> >
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin
> > > [2]
> > >
> >
> http://events.linuxfoundation.org/sites/events/files/slides/Jenkins_at_ASF_2014.pdf
> > >
> > > On Tue, Jan 20, 2015 at 2:57 PM, Robert Metzger <rmetzger@apache.org>
> > > wrote:
> > > > Hi,
> > > >
> > > > it seems that our master is currently not building. See:
> > > > https://travis-ci.org/apache/flink/jobs/47689754
> > > >
> > > > We need to come up with a good solution to notify dev@flink when
> > builds
> > > on
> > > > Travis are failing.
> > > >
> > > > We also had unstable builds recently due to too short akka timeouts
> and
> > > it
> > > > took some time to realize that.
> > > >
> > > > Usually, travis has a pretty good email notification system, but
> thats
> > > not
> > > > working for us because the repository is owned by the "apache" github
> > > user.
> > > > I think only users with admin permissions at "apache/flink" are
> > notified
> > > by
> > > > email from travis.
> > > >
> > > > There are certainly ways to fix this. Right now, the best approach is
> > > > probably setting up a REST 2 e-mail service somewhere which is
> mailing
> > to
> > > > our dev@ list (
> > > > http://docs.travis-ci.com/user/notifications/#Webhook-notification).
> > > >
> > > >
> > > > Robert
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message