Remove the post-deploy checkPing1 (UrlCheck against http://100.70.193.97:8087/api/status) from the hermes environment pipeline so future stack-deploys no longer fail on a flaky health probe.
Changes
backend/configs/hermes.py
Comment out the checkPing1 = UrlCheck(...) object (kept for reference / easy re-enable).
Drop checkPing1 from the pipeline=[...] list.
Drop the now-unused UrlCheck from the from steps.checks import ... line.
Rationale
The hermes stack gateway often reports gateway_running=true with a delay or transient auth state that makes the predicate flap during deploys, which surfaces as a pipeline failure even when the stack itself came up healthy. Mirrors the change already applied to backend/configs/hermes_infra.py (same check disabled there).
The DockerSwarmCheck step (stackChecker) is still in the pipeline, so the actual swarm service state is still validated — only the application-layer HTTP probe is skipped.
Refs: same pattern as hermes_infra.py (checkPing1 already commented out there).
## Summary
Remove the post-deploy `checkPing1` (UrlCheck against `http://100.70.193.97:8087/api/status`) from the `hermes` environment pipeline so future stack-deploys no longer fail on a flaky health probe.
## Changes
- `backend/configs/hermes.py`
- Comment out the `checkPing1 = UrlCheck(...)` object (kept for reference / easy re-enable).
- Drop `checkPing1` from the `pipeline=[...]` list.
- Drop the now-unused `UrlCheck` from the `from steps.checks import ...` line.
## Rationale
The `hermes` stack gateway often reports `gateway_running=true` with a delay or transient auth state that makes the predicate flap during deploys, which surfaces as a pipeline failure even when the stack itself came up healthy. Mirrors the change already applied to `backend/configs/hermes_infra.py` (same check disabled there).
The `DockerSwarmCheck` step (`stackChecker`) is still in the pipeline, so the actual swarm service state is still validated — only the application-layer HTTP probe is skipped.
## Diff
```diff
-from steps.checks import SimpleLog, UrlCheck
+from steps.checks import SimpleLog
...
-checkPing1 = UrlCheck(
- url="http://100.70.193.97:8087/api/status",
- expected=lambda obj: obj[..."gateway_running"] == "true" and obj[..."auth_required"] == "true",
-)
+# checkPing1 = UrlCheck(...)
...
- checkPing1,
+ # checkPing1,
logUrls
```
## Verification
- `python3 -c "import ast; ast.parse(open(\"backend/configs/hermes.py\").read())"` → OK
- `python3 -c "import ast; ast.parse(open(\"backend/configs/hermes.py\").read())"` ✓
- 1 file, +6 / -6.
Refs: same pattern as hermes_infra.py (checkPing1 already commented out there).
Remove checkPing1 (UrlCheck against the gateway /api/status) from the
hermes environment pipeline and comment the corresponding object out, so
deploys to the hermes stack no longer fail the pipeline on a flaky health
probe.
Mirrors the change already applied to backend/configs/hermes_infra.py
(checkPing1 disabled there too). UrlCheck is no longer referenced from
this config, so drop it from the import.
hermes
changed title from PLACEHOLDER to chore(configs): disable post-deploy health check for hermes stack2026-09-06 17:35:17 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Remove the post-deploy
checkPing1(UrlCheck againsthttp://100.70.193.97:8087/api/status) from thehermesenvironment pipeline so future stack-deploys no longer fail on a flaky health probe.Changes
backend/configs/hermes.pycheckPing1 = UrlCheck(...)object (kept for reference / easy re-enable).checkPing1from thepipeline=[...]list.UrlCheckfrom thefrom steps.checks import ...line.Rationale
The
hermesstack gateway often reportsgateway_running=truewith a delay or transient auth state that makes the predicate flap during deploys, which surfaces as a pipeline failure even when the stack itself came up healthy. Mirrors the change already applied tobackend/configs/hermes_infra.py(same check disabled there).The
DockerSwarmCheckstep (stackChecker) is still in the pipeline, so the actual swarm service state is still validated — only the application-layer HTTP probe is skipped.Diff
Verification
python3 -c "import ast; ast.parse(open(\"backend/configs/hermes.py\").read())"→ OKpython3 -c "import ast; ast.parse(open(\"backend/configs/hermes.py\").read())"✓Refs: same pattern as hermes_infra.py (checkPing1 already commented out there).
PLACEHOLDERto chore(configs): disable post-deploy health check for hermes stack