+1 So far, I've been able to commit to Python SDK without caring much about Travis. At least for now, it's not too hard to do testing locally in rare cases where Jenkins is not stable. Hopefully Jenkins will become more stable/faster over time.
- Cham On Sun, Apr 30, 2017 at 10:19 AM Dan Halperin <[email protected]> wrote: > 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 <[email protected]> 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 <[email protected]> > > wrote: > > > > > > Big +1 > > > > > >> On 29. Apr 2017, at 07:21, Robert Bradshaw > <[email protected]> > > wrote: > > >> > > >> On Fri, Apr 28, 2017 at 9:56 PM, Jean-Baptiste Onofré < > [email protected]> > > 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 > > > > > >
