Files
flights_web/.gitea/workflows/release-verify.yml
T
gnezim 36bb2d970f
ci-deploy / build-deploy-test (push) Failing after 9m19s
ci: drop e2e block from release-verify, keep customer-URL smoke check
The e2e suite is intentionally not run against the customer build —
parity gaps are tracked separately, so spending 30 minutes hitting
flights-ui.devwebzavod.ru with Playwright after every Jenkins deploy
adds noise without signal.

What stays: hosts override + wait-for-url + /api diagnose. Together
those still verify that Jenkins's deploy is reachable and that /api
responds with JSON, which is the meaningful post-deploy gate.

Removed: pnpm install, Playwright browser install, the Playwright
test step itself, the playwright-report artifact upload, and the
/api cache pre-warm (its only purpose was warming nginx for the e2e
suite). Updated header + telegram messages to reflect the new
workflow shape.
2026-04-28 09:02:56 +03:00

61 lines
2.6 KiB
YAML

name: release-verify
# Workflow C: run after Jenkins has finished building (operator triggers manually).
# Smoke-checks that http://flights-ui.devwebzavod.ru is alive and that its /api
# wiring responds — the e2e suite is intentionally NOT run here (parity gaps
# against the customer build are tracked separately).
on:
workflow_dispatch:
jobs:
verify:
runs-on: ubuntu-latest
timeout-minutes: 30
env:
TELEGRAM_BOT_TOKEN: ${{ secrets.TELEGRAM_BOT_TOKEN }}
TELEGRAM_CHAT_ID: ${{ secrets.TELEGRAM_CHAT_ID }}
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Notify start
if: ${{ env.TELEGRAM_BOT_TOKEN != '' }}
run: scripts/ci/notify-telegram.sh start release-verify
- name: Add hosts entry for customer URL
# `flights-ui.devwebzavod.ru` has no public DNS — operator hosts
# resolve it via local /etc/hosts to 46.235.186.67 (the customer's
# web ingress IP). Mirror that override on the runner so curl can
# reach the host. Without this, every probe fails with
# `Could not resolve host`.
run: echo "46.235.186.67 flights-ui.devwebzavod.ru" | sudo tee -a /etc/hosts
- name: Wait for customer URL
id: wait_customer
run: scripts/ci/wait-for-url.sh http://flights-ui.devwebzavod.ru/ru-ru/onlineboard 60 5
- name: Diagnose customer URL reachability
id: customer_diag
# Mirrors ci-deploy's tunnel-reachability probe but against the
# customer URL — proves /api wiring is intact post-Jenkins.
run: |
echo "--- /api/health ---"
curl -sSI --max-time 10 http://flights-ui.devwebzavod.ru/api/health | head -10 || true
echo "--- /api/dictionary/1/world_regions (expect JSON, ~5KB) ---"
curl -sS --max-time 10 \
-w "\n[size=%{size_download} time=%{time_total}s code=%{http_code}]\n" \
http://flights-ui.devwebzavod.ru/api/dictionary/1/world_regions | head -c 400; echo
echo "--- second hit on the same dict (expect HIT if nginx caches) ---"
curl -sSI --max-time 10 \
http://flights-ui.devwebzavod.ru/api/dictionary/1/world_regions | grep -iE "^HTTP|x-cache|x-envoy" || true
- name: Notify (success)
if: success() && env.TELEGRAM_BOT_TOKEN != ''
run: scripts/ci/notify-telegram.sh ok release-verify "customer URL reachable + /api responsive"
- name: Notify (failure)
if: failure() && env.TELEGRAM_BOT_TOKEN != ''
run: scripts/ci/notify-telegram.sh fail release-verify "customer URL probe failed — see Gitea run"