Added all tests for testing on travis-ci

[ghost]

• Done adding tests (tests python version and checks if corpora is installed or not).
• Corresponding issue: /cltk/issues/202
• Corresponding build: /achaitanyasai/cltk_docker/builds/116673836

And now this repo can be integrated with travis-ci.

[ghost]

Thank you sir.

[kylepjohnson]

Thank you! I won't have time to think more about this for a few days. In your opinion, what work remains for this Docker work?

[ghost]

I think we can do more like mentioned in the main issue #178 we can add cltk_front end and make it serve as a web server.

[kylepjohnson]

Question: When we build a new container here, can we auto-deploy to Docker Hub?

And will we need to trigger anything manually when a new CLTK release is made?

[ghost]

When we build a new container here, can we auto-deploy to Docker Hub?

Yes, yesterday when I was looking travis documentation for Docker, I found this feature, but I didn't go deep into it. I will try it out.

And will we need to trigger anything manually when a new CLTK release is made?

Yes we need to build a new image manually based on the new CLTK version. Because, the CLTK gets installed into the container using pip rather than from source.
EDIT These are the temporary answers which I feel right now, they may be incorrect. So I will clarify / confirm more about these questions tomorrow.

[kylepjohnson]

@achaitanyasai Understood that these are temporary answers, they're appreciated. Let's both do a little research and share what we learn

In the long run, here is what we will want: 1 container for each of our main CLTK software suites (cltk, cltk_api, and cltk_frontend). These will be 3 different containers on Docker Hub. Ideally, everything will build automatically, upon the creation of a new tagged version of the software.

FYI this might mean that we have 3 docker repos OR we keep the Dockerfiles and related scripts in their respective projects.

Thanks a million!

[ghost]

Let's both do a little research and share what we learn

Yeah sure thank you, right now I am looking into it and get back once I figured out something.

Yes we want 3 different containers. And I think cltk_frontend took care of building docker container already but cltk_api doesn't.

And by the way can you enable Travis-ci service for this repo.

[kylepjohnson]

Travis enabled! Would you please check the build and add a badge to the README?

[ghost]

Yeah sure.
And by the way, as I am busy in writing the proposal and searching the corpus, I didn't look into the above question. I will get back to it soon.

[ghost]

• Done adding badge to README. But I am unable to check build. I mean I am unable to find branches/pull requests/build history in https://travis-ci.org/cltk/cltk_docker/branches
• Also when I am trying to build my forked repo : https://travis-ci.org/achaitanyasai/cltk_docker
  two builds start simultaneously. One build is my actual build and other is from you : https://travis-ci.org/achaitanyasai/cltk_docker/builds
  Is there some thing wrong ?
• Also I am opening a new issue for discussing about auto-deployment to dockerhub.