Travis failures

[prvst]

I noticed that some repositories are failing in the Travis test. The docker images build correctly, the software inside works OK, and the DockerHub also reports no error. Investigating a little better I found that those repositories failed because Travis went out of space during the test, see below.

This is part of the log from Travis while building MSAmanda container:

Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
Untar re-exec error: exit status 1: output: write /usr/share/mime/packages/freedesktop.org.xml: no space left on device
+echo 1
+save_and_shutdown
+'[' '!' -f /home/travis/build/BioDocker/MSAmanda/.exit_code ']'
+set +e
++jobs -p
+kill -9 104
+halt -f
[  390.840000] System halted.
The command "./run 'docker build -t test 1.0.0.5242/.'" exited with 1.

[bgruening]

We can always try different services like https://circleci.com/docs/docker or https://www.shippable.com/. They are more specialised on Docker containers as far as I know.

[ypriverol]

@bgruening doing some checking I saw that https://circleci.com/pricing is free if we run only one containers at a time. One things of using https://www.shippable.com/ is the API access for future developments. From user experience here some benchmark: http://www.slant.co/topics/186/compare/~circleci_vs_travis_vs_shippable. @Leprevost what about try circleci https://circleci.com/integrations/docker. @bgruening which system is Galaxy using.

P.S @Leprevost we should use the new account biodockers@gmail.com

[bgruening]

@ypriverol The Galaxy Docker project is currently evaluating different solutions. No clear answer yet. The Galaxy project is using Travis, Docker is here not needed.

[ypriverol]

Should we keep travis and we can move both togethers ...

[prvst]

@bgruening hum, didn't heard about circleci, I will check that, thanks.

[ypriverol]

@Leprevost can we start the integration with travis and specify the size need to run the tests and the run limitations?

[sauloal]

@Leprevost & @ypriverol I've been digging. If we are setting webhooks to re-create the images upon commits and dockerhub will run the dockerfiles and report the result ( https://docs.docker.com/docker-hub/builds/#webhooks ). why do we need travis?

[prvst]

i still kinda new to travis, so i'm not sure about this. I checked some forums and people are saying that this is a feature/bug from this service. Well, we do use the automatic build system that checks the containers and the images, i think that with travis we can add more tests to evaluate the containers if we want to.

On Thu, Aug 20, 2015 at 12:38 PM Saulo notifications@github.com wrote:

@Leprevost https://github.com/Leprevost & @ypriverol https://github.com/ypriverol I've been digging. If we are setting webhooks to re-create the images upon commits and dockerhub will run the dockerfiles and report the result ( https://docs.docker.com/docker-hub/builds/#webhooks ). why do we need travis?

— Reply to this email directly or view it on GitHub https://github.com/BioDocker/biodocker/issues/5#issuecomment-133070336.

[sauloal]

@Leprevost , travis will spin a virtual machine and run a series of commands as defined in a travis file dockerhub will sping a docker vm and run a series of commands as defined in a dockerfile file.

the only difference is the fact that travis email you. dockerhub can send you a HTTP post with the full log and result of running the dockerfile. if you dockerfile includes a series of tests, if a test fails the docker command fails.

that said, using travis implies that you will have to copy and adapt all the commands you have already tested in the dockerfile. I had huge problems adapting my program from ubuntu 14 to ubuntu 12 (different gcc versions).

[prvst]

do you think we can drop travis then?

On Thu, Aug 20, 2015 at 10:11 PM Saulo notifications@github.com wrote:

@Leprevost https://github.com/Leprevost , travis will spin a virtual machine and run a series of commands as defined in a travis file dockerhub will sping a docker vm and run a series of commands as defined in a dockerfile file.

the only difference is the fact that travis email you. dockerhub can send you a HTTP post with the full log and result of running the dockerfile. if you dockerfile includes a series of tests, if a test fails the docker command fails.

that said, using travis implies that you will have to copy and adapt all the commands you have already tested in the dockerfile. I had huge problems adapting my program from ubuntu 14 to ubuntu 12 (different gcc versions).

— Reply to this email directly or view it on GitHub https://github.com/BioDocker/biodocker/issues/5#issuecomment-133246599.

[sauloal]

I think so. I can try to create a mock "travis to dockerhub"