10-01-2015, 11:51 PM
When a Travis build dumps its core, it would be great to capture it and possibly upload it somewhere for analysis. For this, we'd need to extend the CIbuild.sh script to pack the core dump together with the executable and volatile sources (Bindings.cpp) and upload it somewhere.
I could provide the webspace needed for the storage, if someone writes the code for the uploader-receiver (PHP), I'm not good at writing web stuff. It could be a simple file dropper, with the uploads being accessible through a normal file-system listing. A simple validity checking could be done by using a "cookie" set on Travis via a hidden env variable and checked by the script to disallow bogus uploads.
My motivation for this is driven by these build failures:
https://travis-ci.org/cuberite/cuberite/builds/83114053
https://travis-ci.org/cuberite/cuberite/builds/83114067
(They are for the same commit, yet each fails in the exactly opposite configurations)
I could provide the webspace needed for the storage, if someone writes the code for the uploader-receiver (PHP), I'm not good at writing web stuff. It could be a simple file dropper, with the uploads being accessible through a normal file-system listing. A simple validity checking could be done by using a "cookie" set on Travis via a hidden env variable and checked by the script to disallow bogus uploads.
My motivation for this is driven by these build failures:
https://travis-ci.org/cuberite/cuberite/builds/83114053
https://travis-ci.org/cuberite/cuberite/builds/83114067
(They are for the same commit, yet each fails in the exactly opposite configurations)