You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantin Boudnik <co...@apache.org> on 2015/12/23 08:48:06 UTC
SMTP issue with our CI
Guys,
I am looking at
http://ci.bigtop.apache.org/job/Bigtop-trunk-RAT-check/
and while the build is failing for a reason, fixed yesterday, there's another
issue with it. Namely, there's no SMTP server running on ci.bigtop.apache.org,
so there's no way to send an email. Which will probably lead to the build
failure anyway. I see two options to fix it:
- disable email reports (after all, we should be visiting CI often)
- find a way to send emails by other means. Perhaps, by referring to the VM
host instead of the docker container?
Thoughts?
--
Take care,
Cos
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Cos' pubkey: http://people.apache.org/~cos/cos.asc
---- Wisdom of the hour ----
Re: SMTP issue with our CI
Posted by Konstantin Boudnik <co...@apache.org>.
I put together some pretty ugly hack. Here's what I've done
- Jenkins is configured to send emails to docker0 host address (172.17.42.1)
- host sendmail is now bound to 172.17.42.1 and loopback.
- sendmail relay is limited to only localhost and 172.17 network. The rest
of incoming traffic will be rejected to prevent the spammer from using us
as a relay
This seems to be working just fine, except the the emails are coming from a
noone.nowhere place, but that's crappy JavaMail client not being properly
configured. It can be dealt with by installing some additional plugins to
Jenkins, or something like this. Please chime in if you know any better -
that'd be great!
Thanks,
Cos
On Sat, Feb 06, 2016 at 07:33PM, Konstantin Boudnik wrote:
> Thanks! I believe it should be pretty trivial - all we need is to forward
> port 25 of the Jenkins container to the host's SMTP port.
>
> Cos
>
> On Sat, Feb 06, 2016 at 10:07PM, Ashish Singh wrote:
> > Hi Cos,
> >
> > Let me know if you need any help over here.
> >
> > On 2/6/16, 10:25 AM, "shaposhnik@gmail.com on behalf of Roman Shaposhnik" <shaposhnik@gmail.com on behalf of roman@shaposhnik.org> wrote:
> >
> > >On Fri, Feb 5, 2016 at 11:40 PM, Konstantin Boudnik <co...@apache.org> wrote:
> > >> I've looked at it a bit more and I think our best bet here is to allow Jenkins
> > >> to use host's MTA, which is already configured and should work just fine. This
> > >> way, we aren't going to rely on anything 3rd party. Thoughts?
> > >
> > >Sounds reasonable to me.
> > >
> > >Thanks,
> > >Roman.
> > >
Re: SMTP issue with our CI
Posted by Konstantin Boudnik <co...@apache.org>.
Thanks! I believe it should be pretty trivial - all we need is to forward
port 25 of the Jenkins container to the host's SMTP port.
Cos
On Sat, Feb 06, 2016 at 10:07PM, Ashish Singh wrote:
> Hi Cos,
>
> Let me know if you need any help over here.
>
> On 2/6/16, 10:25 AM, "shaposhnik@gmail.com on behalf of Roman Shaposhnik" <shaposhnik@gmail.com on behalf of roman@shaposhnik.org> wrote:
>
> >On Fri, Feb 5, 2016 at 11:40 PM, Konstantin Boudnik <co...@apache.org> wrote:
> >> I've looked at it a bit more and I think our best bet here is to allow Jenkins
> >> to use host's MTA, which is already configured and should work just fine. This
> >> way, we aren't going to rely on anything 3rd party. Thoughts?
> >
> >Sounds reasonable to me.
> >
> >Thanks,
> >Roman.
> >
Re: SMTP issue with our CI
Posted by Ashish Singh <as...@hortonworks.com>.
Hi Cos,
Let me know if you need any help over here.
Regards,
Ashish Singh
============================
On 2/6/16, 10:25 AM, "shaposhnik@gmail.com on behalf of Roman Shaposhnik" <shaposhnik@gmail.com on behalf of roman@shaposhnik.org> wrote:
>On Fri, Feb 5, 2016 at 11:40 PM, Konstantin Boudnik <co...@apache.org> wrote:
>> I've looked at it a bit more and I think our best bet here is to allow Jenkins
>> to use host's MTA, which is already configured and should work just fine. This
>> way, we aren't going to rely on anything 3rd party. Thoughts?
>
>Sounds reasonable to me.
>
>Thanks,
>Roman.
>
Re: SMTP issue with our CI
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Feb 5, 2016 at 11:40 PM, Konstantin Boudnik <co...@apache.org> wrote:
> I've looked at it a bit more and I think our best bet here is to allow Jenkins
> to use host's MTA, which is already configured and should work just fine. This
> way, we aren't going to rely on anything 3rd party. Thoughts?
Sounds reasonable to me.
Thanks,
Roman.
Re: SMTP issue with our CI
Posted by Konstantin Boudnik <co...@apache.org>.
I've looked at it a bit more and I think our best bet here is to allow Jenkins
to use host's MTA, which is already configured and should work just fine. This
way, we aren't going to rely on anything 3rd party. Thoughts?
Cos
On Wed, Dec 23, 2015 at 12:20PM, Konstantin Boudnik wrote:
> On Wed, Dec 23, 2015 at 08:19PM, Olaf Flebbe wrote:
> > Hi Cos,
> >
> > Nope, we do not need a SMTP Server we need a valid SMTP Client configuration.
> >
> > http://ci.bigtop.apache.org/configure
> >
> > Perhaps we can work something out with INFRA or AWS has something in place for us.
>
> Good point. build.apache.org is able to send the email notifications, perhaps
> we might be able to get the same feature... I will try to catch those guys on
> the chat and see if this can be done...
>
> Thanks for the idea
> Cos
>
> >
> > Olaf
> >
> >
> > > Am 23.12.2015 um 08:48 schrieb Konstantin Boudnik <co...@apache.org>:
> > >
> > > Guys,
> > >
> > > I am looking at
> > > http://ci.bigtop.apache.org/job/Bigtop-trunk-RAT-check/
> > >
> > > and while the build is failing for a reason, fixed yesterday, there's another
> > > issue with it. Namely, there's no SMTP server running on ci.bigtop.apache.org,
> > > so there's no way to send an email. Which will probably lead to the build
> > > failure anyway. I see two options to fix it:
> > > - disable email reports (after all, we should be visiting CI often)
> > > - find a way to send emails by other means. Perhaps, by referring to the VM
> > > host instead of the docker container?
> > >
> > > Thoughts?
> > > --
> > > Take care,
> > > Cos
> > > 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
> > > Cos' pubkey: http://people.apache.org/~cos/cos.asc
> > >
> > > ---- Wisdom of the hour ----
> > >
> >
>
>
Re: SMTP issue with our CI
Posted by Konstantin Boudnik <co...@apache.org>.
On Wed, Dec 23, 2015 at 08:19PM, Olaf Flebbe wrote:
> Hi Cos,
>
> Nope, we do not need a SMTP Server we need a valid SMTP Client configuration.
>
> http://ci.bigtop.apache.org/configure
>
> Perhaps we can work something out with INFRA or AWS has something in place for us.
Good point. build.apache.org is able to send the email notifications, perhaps
we might be able to get the same feature... I will try to catch those guys on
the chat and see if this can be done...
Thanks for the idea
Cos
>
> Olaf
>
>
> > Am 23.12.2015 um 08:48 schrieb Konstantin Boudnik <co...@apache.org>:
> >
> > Guys,
> >
> > I am looking at
> > http://ci.bigtop.apache.org/job/Bigtop-trunk-RAT-check/
> >
> > and while the build is failing for a reason, fixed yesterday, there's another
> > issue with it. Namely, there's no SMTP server running on ci.bigtop.apache.org,
> > so there's no way to send an email. Which will probably lead to the build
> > failure anyway. I see two options to fix it:
> > - disable email reports (after all, we should be visiting CI often)
> > - find a way to send emails by other means. Perhaps, by referring to the VM
> > host instead of the docker container?
> >
> > Thoughts?
> > --
> > Take care,
> > Cos
> > 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
> > Cos' pubkey: http://people.apache.org/~cos/cos.asc
> >
> > ---- Wisdom of the hour ----
> >
>
Re: SMTP issue with our CI
Posted by Olaf Flebbe <of...@oflebbe.de>.
Hi Cos,
Nope, we do not need a SMTP Server we need a valid SMTP Client configuration.
http://ci.bigtop.apache.org/configure
Perhaps we can work something out with INFRA or AWS has something in place for us.
Olaf
> Am 23.12.2015 um 08:48 schrieb Konstantin Boudnik <co...@apache.org>:
>
> Guys,
>
> I am looking at
> http://ci.bigtop.apache.org/job/Bigtop-trunk-RAT-check/
>
> and while the build is failing for a reason, fixed yesterday, there's another
> issue with it. Namely, there's no SMTP server running on ci.bigtop.apache.org,
> so there's no way to send an email. Which will probably lead to the build
> failure anyway. I see two options to fix it:
> - disable email reports (after all, we should be visiting CI often)
> - find a way to send emails by other means. Perhaps, by referring to the VM
> host instead of the docker container?
>
> Thoughts?
> --
> Take care,
> Cos
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
> Cos' pubkey: http://people.apache.org/~cos/cos.asc
>
> ---- Wisdom of the hour ----
>