I don't know much about this particular tool, but something like this would be good.
Our current toolchain, with HadoopQA needing a JIRA patch and our code reviews mostly migrating to Github is really awkward to deal with, so TravisCI's Github integration's a definite plus. An example of Tephra's integration is here[1]: and on TravisCI's home page[2] they mention that open source projects are free. Assuming there are no licensing, scalability or implementation gotchas I'd be a +1. Geoffrey [1] https://travis-ci.org/apache/incubator-tephra [2] https://travis-ci.org/ On Tue, May 28, 2019 at 1:31 PM William Shen <[email protected]> wrote: > +1 It would be awesome to be able to do this. > Any concerns if we choose to run long IT as part of this setup? > > On Tue, May 28, 2019 at 1:00 PM Pedro Boado <[email protected]> wrote: > > > What IT would you suggest to run? Testsuite (including long IT) takes > ~2h. > > > > On Tue, 28 May 2019, 20:40 Thomas D'Silva, <[email protected] > > .invalid> > > wrote: > > > > > +1 I think its a great idea. This would make it easier for new > > contributors > > > to run tests > > > and also make it easier for committers to verify a patch doesn't break > > > functionality. > > > > > > On Tue, May 28, 2019 at 12:34 PM Priyank Porwal < > [email protected] > > > > > > wrote: > > > > > > > Hi, > > > > > > > > What do you guys think about this work to setup Travis-CI and > > > CodeCoverage > > > > for Phoenix? The objective would be to run unit and integration tests > > on > > > > each PR, show code-coverage reports and perhaps also do checkstyle > > checks > > > > (after initial scrubbing effort). This would help rid of manual patch > > > > uploads that we need currently, plus bring visibility into code > health. > > > > Thoughts? > > > > > > > > https://issues.apache.org/jira/browse/PHOENIX-4863 > > > > > > > > Thanks, > > > > Priyank > > > > > > > > > >
