Change CI doc builds to upload artifacts even when the build fails #76
Comments
3 tasks
rapids-bot bot
pushed a commit
to rapidsai/cudf
that referenced
this issue
Dec 13, 2024
Contributes to #7795. Also contributes to rapidsai/build-planning#76. Authors: - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - Nghia Truong (https://github.com/ttnghia) - Yunsong Wang (https://github.com/PointKernel) - Bradley Dice (https://github.com/bdice) - David Wendt (https://github.com/davidwendt) URL: #17545
|
A first example of this is done in rapidsai/cudf#17545 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sphinx builds often fail in non-fatal ways. For example, the documentation may be produced with rendering issues. Diagnosing these issues in CI can be challenging because the produced documentation is not currently published unless the build succeeds. We should modify the doc build jobs to upload the documentation even if the build fails to make debugging easier. This can be done by adding
set +ebefore themake html/sphinx-buildinvocation, saving the exit code, and triggering the upload before returning the resulting exit code.The text was updated successfully, but these errors were encountered: