I know the primary travis build logs are available on the web and with the logs
command in the travis command line client, but I was wondering if there is a way to access other files generated as part of the build process, such as the file /home/travis/.rvm/log/1391454748_rbx-2.2.4/rubygems.install.log
referenced in https://travis-ci.org/rspec/rspec-its/jobs/18148204
相关问题
- How to specify memcache server to Rack::Session::M
- Why am I getting a “C compiler cannot create execu
- reference to a method?
- ruby 1.9 wrong file encoding on windows
- gem cleanup shows error: Unable to uninstall bundl
相关文章
- Ruby using wrong version of openssl
- Difference between Thread#run and Thread#wakeup?
- how to call a active record named scope with a str
- Best way to manage docker containers with supervis
- “No explicit conversion of Symbol into String” for
- Segmentation fault with ruby 2.0.0p247 leading to
- How to detect if an element exists in Watir
- Build errors of missing packages in Visual Studio
Those files are lost once the build is finished. If you want to read them, you should add a
cat
command to print out to the log you see.If the install command is failing, then you should override
install
to install the gem for which the installation is failing:banzaiman's answer is good (it helped me!). But if you use:
then the
cat
command will likely succeed, and so the line above will count as as success, and the build will continue. If you want the build to fail when the install fails, then you need to make sure the line has a non-zero exit status. So do something like this:The expression in curly braces will be run only if the
gem install XXX
fails (i.e., has a non-zero exit status).cat
will presumably succeed, so the command after the&&
will be run. That1
ensures a non-zero exit status for the whole line, causing the build to stop at that point.Note the necessary whitespace around the curly braces.