I emailed support at travis, and the travis-ci people enabled debug on my build. https://docs.travis-ci.com/user/running-build-in-debug-mode/
With the debug mode I could ssh in and run the individual steps of the build. What I saw when debugging, was that the build progresses right through the place it was stuck in the regular build. Ie I run the commands travis_run_before_install (which does nothing for my build) travis_run_install (which runs "mvn install" and "warms up" the local VM's local maven repo) travis_run_before_script (which installs the sonarcloud stuff) travis_run_script (which does the sonarcloud and cobertura/coveralls builds and runs the pax exam test in the sonarcloud phase) All of the above run without any errors. In the regular travis-ci build travis_run_script got stuck waiting for apache karaf to boot in a pax exam integration test, but in debug it runs right through that test without getting stuck (same as my local maven builds). Could it be that I have somehow activated a tty dependency in karaf?
