View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0036916 | mantisbt | tools | public | 2026-03-06 13:04 | 2026-04-08 18:54 |
| Reporter | dregad | Assigned To | dregad | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Target Version | 2.29.0 | Fixed in Version | 2.29.0 | ||
| Summary | 0036916: GitHub Actions CI builds should fail during install phase | ||||
| Description | Currently, a failure to install MantisBT is detected by the GitHub Action CI builds during the subsequent phase "Post-installation steps" as it generally impossible to complete it if the database is not setup correctly. Job should fail right away during the installation phase if an error occurs. | ||||
| Tags | No tags attached. | ||||
|
MantisBT: master b9875b12 2026-03-06 12:44 Details Diff |
GHA: return error code from curl if install fails Until now, a failure to install MantisBT was detected by the CI builds during the subsequent phase "Post-installation steps" as it generally impossible to complete it if the database is not setup correctly. With this change, if the MantisBT installer exits with an HTTP error code (>= 400), curl will fail with an exit code 22. The --fail-with-body option allows displaying the installer's output. That allows GitHub Actions to catch the error when it occurs, during the "Install MantisBT" phase. Fixes 0036916 |
Affected Issues 0036916 |
|
| mod - build/ci_install_mantis.sh | Diff File | ||
