We should add support for Travis CI so all our Pull Requests, branches, and pushes are automatically built. It will help us avoid bad merges and will show the build: passing icon in the main page.
I have played with it a little bit but didn't manage to arrive to a correct .travis.yml file. There are two things I'd like to do with it:
- Either install everything and execute the web server to make sure there are no Python non-runtime errors
- Or have it build from the
Dockerfile and run it
Of course, when we have tests, we can also run the tests there.
I managed to do the first one, however, the web server is running non-stop and therefore the build never stops. Any ideas on how to fix that?
About the second one, I will try some more, but running docker inside docker inside a VM can be complex and still has the same issues as before (web server never quits).
We should add support for Travis CI so all our Pull Requests, branches, and pushes are automatically built. It will help us avoid bad merges and will show the
build: passingicon in the main page.I have played with it a little bit but didn't manage to arrive to a correct
.travis.ymlfile. There are two things I'd like to do with it:Dockerfileand run itOf course, when we have tests, we can also run the tests there.
I managed to do the first one, however, the web server is running non-stop and therefore the build never stops. Any ideas on how to fix that?
About the second one, I will try some more, but running docker inside docker inside a VM can be complex and still has the same issues as before (web server never quits).