debugging - What is the current workflow to debug Travis builds locally?

Question

One used to be able to download Vagrant boxes to debug Travis builds (for GitHub projects for instance). Apparently, this is no longer possible, so how do people currently debug complex Travis build chains locally?

question from:https://stackoverflow.com/questions/20544803/what-is-the-current-workflow-to-debug-travis-builds-locally

Answer 1

One way to inspect the build (not to debug, sorry) is to send the build logs to another server on failure.

Here is an example:

after_failure
  - sudo tar -czf /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz your-application-logs/
  - scp /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz travis@your-server.com:~/logs

You could send them via email, store them on a storage server or whatever.

These logs would be useful to you if you run your tests in a debug mode and include our own logs as well in the tarball.