Related, but a bit off-topic: has anybody setup a Bean Pipeline CI against the different runners?
I normally do this against a custom Docker-based setup, but just against Spark. Probably it'd be very interesting to run a pipeline against different runners to get broader conclusions. If anybody has worked on a similar idea, I'd appreciate to discuss it. Thanks in advance. On Mon, Oct 24, 2016 at 2:37 AM, Frances Perry <[email protected]> wrote: > Jason recently started documenting the project's testing setup. See > http://beam.incubator.apache.org/contribute/testing/ > > On Sat, Oct 22, 2016 at 11:18 PM, Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi > > > > We use both Jenkins and Travis. > > > > Jenkins is on build.apache.org and you can find Travis yml in source. > > > > Regards > > JB > > > > > > > > On Oct 22, 2016, 21:56, at 21:56, Neelesh Salian <[email protected]> > > wrote: > > >Hello, > > > > > >I wanted to check to see if there is continuous integration service > > >used to > > >build and test Beam similar to Travis. > > >Would certainly help speed up adding code to the project. > > > > > >Thank you in advance. > > > > > >-- > > >Neelesh Srinivas Salian > > >Engineer > > > -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
