>From there, I see there is better integration with Github that can be used if you opt-in: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
On Fri, Jan 8, 2016 at 4:15 PM Gino Bustelo <[email protected]> wrote: > Based on > https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci, it > seems that we could continue to use travisci. I honestly prefer Travis > since the configuration is all contained within our project. > > On Fri, Jan 8, 2016 at 3:55 PM, Reynold Xin <[email protected]> wrote: > > > ASF does have a Jenkins infrastructure. You can use that as an option. > > > > https://builds.apache.org/ > > > > On Fri, Jan 8, 2016 at 9:54 AM, Chip Senkbeil <[email protected]> > > wrote: > > > > > I know that Apache Spark uses Jenkins with a plugin in Github to allow > > them > > > to manually invoke Jenkins testing against PRs. > > > > > > Do we want something similar (or do we have it already) for Toree? > > > Currently, we use Travis CI, which is free for open source projects. I > > > don't know off the top of my head if Travis allows you to manually > invoke > > > builds/tests againsts PRs. > > > > > > Is there something specific that Apache requires us to use? Does anyone > > > have a preference in how we handle PRs? > > > > > > Also, I was reading over (https://www.apache.org/dev/release.html). > > There > > > are multiple release types including nightly builds. While we don't > > > advertise nightly builds on the main site, it would be useful to have > > > nightly builds for those interested in trying bug fixes, getting new > > > features, etc. This is especially important considering we currently > ask > > > all users to build from source; so, moving to a release model changes > our > > > flow a little bit. > > > > > > Is there available Apache tooling for nightly builds? Do we need to set > > > something up ourselves? > > > > > >
