I would not mind moving to jenkins - fairly common platform and well known (So is Travis are you going to say ;-)) Travis is also very well integrated with the new Github work flow and marketplace.
-- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Jul 3, 2017 at 3:42 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > yes, mentionned in another thread that PR usage need to probably move to > jenkins of travis to have that. In any case (if we want to maintain > buildbot too) we need to ask infra since they are the ones owning that part > until we use travis. > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://blog-rmannibucau.rhcloud.com> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2017-07-03 15:32 GMT+02:00 Jean-Louis Monteiro <jlmonte...@tomitribe.com>: > > > Is anyone aware of the apache configuration to get buildbot to build our > > Github PRs? > > > > Not sure it's working or even configured at the moment. > > I've see this https://github.com/Kami/node-buildbot-github > > and a couple of other Apache blog postes. > > > > Would be very helpful. > > > > JLouis > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > >
