You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Suneel Marthi <su...@gmail.com> on 2015/04/17 00:23:40 UTC
[VOTE] Add Travis-CI for Mahout
Would this be an additional CI we would like to add to Mahout ?
https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
I am up for it.
+1
Re: [VOTE] Add Travis-CI for Mahout
Posted by Yash Sharma <ya...@gmail.com>.
3gigs of memory and 50mins runtime is the upper bound for Travis. We
explored Travis for Drill but could not continue with it because few of
our testcases were resource hungry.
If Mahout fits in these Travis is a great tool.
-Via mobile. Excuse brevity.
On 17 Apr 2015 10:03 pm, "Pat Ferrel" <pa...@occamsmachete.com> wrote:
> Good question. It can replace Jenkins, integrates automatically (only I
> think) with Github, and is orders of magnitude easier to use than Jenkins.
> A lot of other projects use it but I was surprised to hear Apache favored
> it. Doesn’t Apache have some draconian requirement to control all bits of
> the project pipeline and workflow?
>
> In our case would it be able to replace Jenkins or is it extra work?
>
> BTW slightly off topic... the Slack thing is set up for Apache.org. It
> requires you to have an @apache.org email. That means other projects can
> create their own channel. It is also gratis and so will eventually be
> overwhelmed if lots of other projects start using it.
>
> On Apr 17, 2015, at 12:31 AM, Stevo Slavić <ss...@gmail.com> wrote:
>
> Before I cast my vote can somebody please explain which problem are we
> trying to or expect from this to be solved?
>
> Kind regards,
> Stevo Slavic.
> On Apr 17, 2015 9:22 AM, "Ted Dunning" <te...@gmail.com> wrote:
>
> > Totally simple if the project has a standard build/test structure.
> >
> > For t-digest it took about 4 lines of yaml checked into the root
> > directory. The documentation on travis is excellent and the process of
> > setup is easy.
> >
> >
> > On Fri, Apr 17, 2015 at 3:27 AM, Andrew Musselman <
> > andrew.musselman@gmail.com> wrote:
> >
> >> Worth trying out though I've never used Travis; what work effort is
> >> required, any idea?
> >>
> >> On Thursday, April 16, 2015, Suneel Marthi <su...@gmail.com>
> >> wrote:
> >>
> >>> Would this be an additional CI we would like to add to Mahout ?
> >>>
> >>> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
> >>>
> >>> I am up for it.
> >>>
> >>> +1
> >>>
> >>
> >
>
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Andrew Musselman <an...@gmail.com>.
+1
On Tuesday, April 21, 2015, Andrew Palumbo <ap...@outlook.com> wrote:
> +1 I think that it would free up developer resources. especially now that
> we're working on 2 branches.
>
>
> On 04/17/2015 06:41 PM, Ted Dunning wrote:
>
>> On Fri, Apr 17, 2015 at 6:32 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>>
>> Doesn’t Apache have some draconian requirement to control all bits of the
>>> project pipeline and workflow?
>>>
>>
>> No. Apache has a strict policy about *hosting* all of the bits that users
>> of the software consume. That means that authoritative version history.
>> And the released bits. Using outside tools either automated or manual is
>> a
>> fine thing.
>>
>>
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Andrew Palumbo <ap...@outlook.com>.
+1 I think that it would free up developer resources. especially now
that we're working on 2 branches.
On 04/17/2015 06:41 PM, Ted Dunning wrote:
> On Fri, Apr 17, 2015 at 6:32 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> Doesn’t Apache have some draconian requirement to control all bits of the
>> project pipeline and workflow?
>
> No. Apache has a strict policy about *hosting* all of the bits that users
> of the software consume. That means that authoritative version history.
> And the released bits. Using outside tools either automated or manual is a
> fine thing.
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Ted Dunning <te...@gmail.com>.
On Fri, Apr 17, 2015 at 6:32 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> Doesn’t Apache have some draconian requirement to control all bits of the
> project pipeline and workflow?
No. Apache has a strict policy about *hosting* all of the bits that users
of the software consume. That means that authoritative version history.
And the released bits. Using outside tools either automated or manual is a
fine thing.
Re: [VOTE] Add Travis-CI for Mahout
Posted by Pat Ferrel <pa...@occamsmachete.com>.
Good question. It can replace Jenkins, integrates automatically (only I think) with Github, and is orders of magnitude easier to use than Jenkins. A lot of other projects use it but I was surprised to hear Apache favored it. Doesn’t Apache have some draconian requirement to control all bits of the project pipeline and workflow?
In our case would it be able to replace Jenkins or is it extra work?
BTW slightly off topic... the Slack thing is set up for Apache.org. It requires you to have an @apache.org email. That means other projects can create their own channel. It is also gratis and so will eventually be overwhelmed if lots of other projects start using it.
On Apr 17, 2015, at 12:31 AM, Stevo Slavić <ss...@gmail.com> wrote:
Before I cast my vote can somebody please explain which problem are we
trying to or expect from this to be solved?
Kind regards,
Stevo Slavic.
On Apr 17, 2015 9:22 AM, "Ted Dunning" <te...@gmail.com> wrote:
> Totally simple if the project has a standard build/test structure.
>
> For t-digest it took about 4 lines of yaml checked into the root
> directory. The documentation on travis is excellent and the process of
> setup is easy.
>
>
> On Fri, Apr 17, 2015 at 3:27 AM, Andrew Musselman <
> andrew.musselman@gmail.com> wrote:
>
>> Worth trying out though I've never used Travis; what work effort is
>> required, any idea?
>>
>> On Thursday, April 16, 2015, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>>> Would this be an additional CI we would like to add to Mahout ?
>>>
>>> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
>>>
>>> I am up for it.
>>>
>>> +1
>>>
>>
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Stevo Slavić <ss...@gmail.com>.
Before I cast my vote can somebody please explain which problem are we
trying to or expect from this to be solved?
Kind regards,
Stevo Slavic.
On Apr 17, 2015 9:22 AM, "Ted Dunning" <te...@gmail.com> wrote:
> Totally simple if the project has a standard build/test structure.
>
> For t-digest it took about 4 lines of yaml checked into the root
> directory. The documentation on travis is excellent and the process of
> setup is easy.
>
>
> On Fri, Apr 17, 2015 at 3:27 AM, Andrew Musselman <
> andrew.musselman@gmail.com> wrote:
>
> > Worth trying out though I've never used Travis; what work effort is
> > required, any idea?
> >
> > On Thursday, April 16, 2015, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> > > Would this be an additional CI we would like to add to Mahout ?
> > >
> > > https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
> > >
> > > I am up for it.
> > >
> > > +1
> > >
> >
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Ted Dunning <te...@gmail.com>.
Totally simple if the project has a standard build/test structure.
For t-digest it took about 4 lines of yaml checked into the root
directory. The documentation on travis is excellent and the process of
setup is easy.
On Fri, Apr 17, 2015 at 3:27 AM, Andrew Musselman <
andrew.musselman@gmail.com> wrote:
> Worth trying out though I've never used Travis; what work effort is
> required, any idea?
>
> On Thursday, April 16, 2015, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > Would this be an additional CI we would like to add to Mahout ?
> >
> > https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
> >
> > I am up for it.
> >
> > +1
> >
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Suneel Marthi <su...@gmail.com>.
Its trivial to configure travis for a project if one has the project admin
rights. Most github projects are setup with travis.
As Ted's already mentioned there are some bounds with Travis that restrict
how much resources one can consume.
It should be fine for Mahout today though IMO.
On Thu, Apr 16, 2015 at 9:27 PM, Andrew Musselman <
andrew.musselman@gmail.com> wrote:
> Worth trying out though I've never used Travis; what work effort is
> required, any idea?
>
> On Thursday, April 16, 2015, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > Would this be an additional CI we would like to add to Mahout ?
> >
> > https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
> >
> > I am up for it.
> >
> > +1
> >
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Andrew Musselman <an...@gmail.com>.
Worth trying out though I've never used Travis; what work effort is
required, any idea?
On Thursday, April 16, 2015, Suneel Marthi <su...@gmail.com> wrote:
> Would this be an additional CI we would like to add to Mahout ?
>
> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
>
> I am up for it.
>
> +1
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Ted Dunning <te...@gmail.com>.
I use it for t-digest and like it a lot.
There are some strict bounds on how much resource you are supposed to
consume. Mileage may vary.
On Fri, Apr 17, 2015 at 12:23 AM, Suneel Marthi <su...@gmail.com>
wrote:
> Would this be an additional CI we would like to add to Mahout ?
>
> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
>
> I am up for it.
>
> +1
>
Re: [VOTE] Add Travis-CI for Mahout
Posted by Dmitriy Lyubimov <dl...@gmail.com>.
+1
On Thu, Apr 16, 2015 at 3:23 PM, Suneel Marthi <su...@gmail.com>
wrote:
> Would this be an additional CI we would like to add to Mahout ?
>
> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
>
> I am up for it.
>
> +1
>