Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/148#issuecomment-158431972
Thanks @PommeVerte - my personal opinion is that there is an order of
things we need in CI:
1. just a basic build/test with `mvn clean install` - that already takes
10-20 minutes on a nice box. that's our early warning system and it should fail
as quickly as possible if it is to fail.
1. support for building PR branches
1. support for integration tests with neo4j
1. all the other awesome automation we could want - doc gen, snapshot
distro, etc.
if we just had 1 and 2, i'd be stoked so i think the PR should focus around
nailing those two things. The rest we could discuss as part of additional JIRA
issues.
> adding support for coveralls could be cool. (test code coverage reports)
use of coveralls might be neat assuming they can aggregate a multi-module
maven project.
> use ant as a basis.
we don't use ant for jenkins - just maven. i don't see much need to
maintain a second build process.
> It will only require a PMC with write rights to this repo to setup the
travis account (or configure it)
i can shutdown the jenkins job when this is merged. i don't have rights to
do the travis setup on the repo. maybe just open a ticket on infra?
anyway, some other questions...we had good experience with travis in the
pre-apache days, but the apache account was jammed. have you looked at the
recent build waits for apache projects (i'm pretty sure they have improved
since we last looked at travis)? also, will we be able to run the integration
tests over travis? with needs for hadoop, zookeeper, etc - how will that work?
finally, i think you should bring up a DISCUSS on dev list and point to
this issue so that others will take notice and have a chance to get in a say
before we move forward in any particular direction.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
