Closes #25. Set up Travis CI and add in a Gradle wrapper.#26
Conversation
|
CI build failed due to test failure fixed in PR #18. Hadoop 2.9 build failed because the proper fsimage files are not set up; I will update. But it looks that overall the Travis integration is working as expected. Very cool! And it builds all of the Hadoop versions in parallel. Great stuff. |
|
have you considered using CircleCI? We have free trial for OSS. The Travis queue is pretty congested. |
| jdk: | ||
| - oraclejdk8 | ||
| env: | ||
| - HADOOP_VERSION=2.7.5 |
There was a problem hiding this comment.
will these run in parallel or one by one ?
|
@oliverhu Is there any benefit to using CircleCI over TravisCI? I know of other LinkedIn projects (Azkaban) using TravisCI, and the integration was exceedingly easy. They also have a committed to be always free for OSS. Does CircleCI have something similar? re: your congestion comment, I don't know if I just got lucky, but all of my tests started in only a few seconds after pushing. |
|
@xkrogen Functionality wise, as far as the functionalities I need, there is no much difference. The major benefit is the queue is much more empty in CircleCI comparing with Travis CI. IIRC, we use free tier for both TravisCI & CircleCI, but 99% of the projects are using TravisCI sharing the same queue. It used to take us 3 hours before any resource is available to check our PRs.. |
|
Looks like in the free tier on CircleCI we cannot take advantage of any parallel execution because only a single container is granted, is that right? This is from CircleCI's website:
Based on this this sentence alone, it seems to me that TravisCI is a better fit. Maybe if we see issues with build time then CircleCI can be further investigated. |
|
Not sure, we only used single execution for macOS containers and the performance was really good. Yeah, just want to point out there are other available CI solutions available. |
|
Thanks for the info @oliverhu ! I suspect that the TravisCI queue with Linux containers instead of macOS may perform better. If we do see issues I'll definitely look into CircleCI. |
|
Also, if their status page is to be trusted, at no point in the last month has there ever been a backlog of Linux open source jobs: https://www.traviscistatus.com/#month |
… proper test files for 2.9.0, and add a travis_wait step to avoid timeouts. Add in 2.6.5 to CI testing Add in proper 2.9 test files travis_wait
… proper test files for 2.9.0, and add a travis_wait step to avoid timeouts.
…p 2.6 build, increase logging for debuggability, and add a status badge. (PR #27)
2 participants
No description provided.