very soon: https://github.com/apache/zookeeper/pull/751
I have pushed the script I am using in other projects, with tests on jdk11 + linux, default profile. We should ask INFRA in order to enable Travis-CI, this is kind of important infrastructural change so I think some PMC should sponsor this and approve Once we have Travis, we can enable https://coveralls.io Code Coverage for free, all of them is well integrated with GitHub. I am doing the same during this days with on of the open source projects from my company (https://github.com/diennea/blazingcache) and it works like a charm. I had set up Coveralls+Jenkins for Apache BookKeeper, it needs an INFRA step because of the management of a shared secret, but with Travis+ Coveralls everything is automatic. Enrico Il giorno mer 2 gen 2019 alle ore 16:09 Enrico Olivelli <eolive...@gmail.com> ha scritto: > > I will sent a PR soon > > this is the Ticket > https://issues.apache.org/jira/browse/ZOOKEEPER-3234 > > Enrico > > Il giorno mer 2 gen 2019 alle ore 15:48 Andor Molnar > <an...@cloudera.com.invalid> ha scritto: > > > > +1 > > > > > > On Sat, Dec 22, 2018 at 2:48 PM Enrico Olivelli <eolive...@gmail.com> wrote: > > > > > Hi, > > > Now that we are Mavenizing ZookKeeper it will be super easy to add > > > Travis-CI to the story. > > > > > > It will enable non Apache Committers to have more access to logs of > > > their patches. > > > > > > I am thinking about Travis only for Pull Requests. > > > It is super easy and ZooKeeper build is not super heavy. > > > > > > I would suggest to run tests with a single degree of parallelism > > > > > > Thoughts ? > > > Enrico > > >
