tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Azuryy Yu <azury...@gmail.com>
Subject Re: TravisCI is too slow.
Date Fri, 06 Mar 2015 05:31:28 GMT
+1 for my patch in future.

On Fri, Mar 6, 2015 at 1:23 PM, Jaehwa Jung <blrunner@apache.org> wrote:

> +1
>
> I also agree with you. :)
>
> 2015-03-06 14:12 GMT+09:00 Jihun Kang <ykrips@gmail.com>:
>
> > I agree. There are 10 build requests on Travis CI, and they are in
> pending
> > state. This situation could delay our development cycles.
> >
> > 2015-03-06 13:58 GMT+09:00 Jihoon Son <jihoonson@apache.org>:
> >
> > > Hi Hyunsik,
> > > +1 for your suggestion.
> > >
> > > Warmly,
> > > Jihoon
> > >
> > > On Fri, Mar 6, 2015 at 1:53 PM Hyunsik Choi <hyunsik@apache.org>
> wrote:
> > >
> > > > Hi folks,
> > > >
> > > > Currently, we usually use Github for review, and Github uses TravisCI
> > > > for automatic CI. But, in these days, TravisCI is too slow. Actually,
> > > > I don't know why. Occasionally, TravisCI has been slow.
> > > >
> > > > So, I'd like to suggest that you guys submit patchs to Jira and mark
> > > > the jira issues as PATCH AVAILABLE. If you do so, ASF jenkins will
> > > > test and comment the test result.
> > > >
> > > > Best regards,
> > > > Hyunsik
> > > >
> > >
> >
>

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