Re: Status of our CI tools

[Etienne Chauchot <ec...@gmail.com>]

Big +1 also,

I've been ignoring Travis for some months also.

I totally agree with what Dan wrote.

Best

Etienne


Le 30/04/2017 à 19:19, Dan Halperin a écrit :
> I think the confusion to new users is much worse than any temporary loss of
> functionality here. +1 * 100!
>
> On Fri, Apr 28, 2017 at 11:00 PM, Mingmin Xu <mi...@gmail.com> wrote:
>
>> +1
>> Have ignored TravisCI for some time as the failures are not related with
>> code/test issues.
>>
>> I still hope TravisCI could work with Beam code repository some day, to
>> run tests before creating a PR.
>>
>> Mingmin
>>
>>> On Apr 28, 2017, at 10:26 PM, Aljoscha Krettek <al...@apache.org>
>> wrote:
>>> Big +1
>>>
>>>> On 29. Apr 2017, at 07:21, Robert Bradshaw <ro...@google.com.INVALID>
>> wrote:
>>>> On Fri, Apr 28, 2017 at 9:56 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>>>> +1
>>>>>
>>>>> Travis is useless and our Jenkins is good IMHO !
>>>> Travis is really useful for the Python SDK, but I'm hopeful that soon
>>>> Jenkins will be stable and quick enough that I won't miss it, and
>>>> having only one CI to deal with should simplify things.
>>>>
>>>> - Robert