You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Noah Slater <ns...@apache.org> on 2013/05/17 15:26:26 UTC
Can we fix or disable Travis CI?
Hi devs,
See this:
https://github.com/apache/couchdb/pull/60
> Failed — The Travis CI build failed (Details)
It's it's current state, Travis CI is meaningless. It fails 50% of the time
or more.
I'm fed up of the bogus emails it sends me, and I think it's sending the
wrong message to people who are doing pull requests.
We should fix it (how? and how much effort) or turn it off in favour of
Jan's Jenkin's setup.
Thoughts?
Thanks,
--
NS
Re: Can we fix or disable Travis CI?
Posted by Dirkjan Ochtman <di...@ochtman.nl>.
On May 17, 2013 7:25 PM, "Dave Cottlehuber" <dc...@jsonified.com> wrote:
> Did we? Mmm it shouldn't fail on that, did I miss some travis-specific
> thingummie?
Looks like the build is now passing on master, at least. I pushed a fix for
a Sphinx warning, but I doubt that was the problem.
Cheers,
Dirkjan
Re: Can we fix or disable Travis CI?
Posted by Dave Cottlehuber <dc...@jsonified.com>.
On 17 May 2013 18:34, Robert Newson <rn...@apache.org> wrote:
> So that's a lot better now, except for R16 which we knew..
Did we? Mmm it shouldn't fail on that, did I miss some travis-specific
thingummie?
A+D
Re: Can we fix or disable Travis CI?
Posted by Robert Newson <rn...@apache.org>.
So that's a lot better now, except for R16 which we knew..
On 17 May 2013 17:25, Robert Newson <rn...@apache.org> wrote:
> Let's try to fix it. I've made a start.
>
> On 17 May 2013 14:28, Garren Smith <ga...@apache.org> wrote:
>> I'm in favour of turning it off unless its really easy to fix.
>>
>>
>> On 17 May 2013, at 3:26 PM, Noah Slater <ns...@apache.org> wrote:
>>
>>> Hi devs,
>>>
>>> See this:
>>>
>>> https://github.com/apache/couchdb/pull/60
>>>
>>>> Failed — The Travis CI build failed (Details)
>>>
>>> It's it's current state, Travis CI is meaningless. It fails 50% of the time
>>> or more.
>>>
>>> I'm fed up of the bogus emails it sends me, and I think it's sending the
>>> wrong message to people who are doing pull requests.
>>>
>>> We should fix it (how? and how much effort) or turn it off in favour of
>>> Jan's Jenkin's setup.
>>>
>>> Thoughts?
>>>
>>> Thanks,
>>>
>>> --
>>> NS
>>
Re: Can we fix or disable Travis CI?
Posted by Robert Newson <rn...@apache.org>.
Let's try to fix it. I've made a start.
On 17 May 2013 14:28, Garren Smith <ga...@apache.org> wrote:
> I'm in favour of turning it off unless its really easy to fix.
>
>
> On 17 May 2013, at 3:26 PM, Noah Slater <ns...@apache.org> wrote:
>
>> Hi devs,
>>
>> See this:
>>
>> https://github.com/apache/couchdb/pull/60
>>
>>> Failed — The Travis CI build failed (Details)
>>
>> It's it's current state, Travis CI is meaningless. It fails 50% of the time
>> or more.
>>
>> I'm fed up of the bogus emails it sends me, and I think it's sending the
>> wrong message to people who are doing pull requests.
>>
>> We should fix it (how? and how much effort) or turn it off in favour of
>> Jan's Jenkin's setup.
>>
>> Thoughts?
>>
>> Thanks,
>>
>> --
>> NS
>
Re: Can we fix or disable Travis CI?
Posted by Garren Smith <ga...@apache.org>.
I'm in favour of turning it off unless its really easy to fix.
On 17 May 2013, at 3:26 PM, Noah Slater <ns...@apache.org> wrote:
> Hi devs,
>
> See this:
>
> https://github.com/apache/couchdb/pull/60
>
>> Failed — The Travis CI build failed (Details)
>
> It's it's current state, Travis CI is meaningless. It fails 50% of the time
> or more.
>
> I'm fed up of the bogus emails it sends me, and I think it's sending the
> wrong message to people who are doing pull requests.
>
> We should fix it (how? and how much effort) or turn it off in favour of
> Jan's Jenkin's setup.
>
> Thoughts?
>
> Thanks,
>
> --
> NS