test(ci): TST-25 Check 6 probe — forced-failure nightly issue path
tst25-check6-probe / nightly-windev-probe (push) Failing after 16s
tst25-check6-probe / nightly-windev-probe (push) Failing after 16s
Temporary branch only. Exercises the nightly-windev on-failure Gitea-issue step in a real workflow run, with the public-origin body link under test.
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
# TEMPORARY — TST-25 acceptance Check 6 probe. Lives only on `test/tst25-check6-nightly-issue`
|
||||
# and is deleted with that branch. It reproduces the `nightly-windev` job's shape (a failing main
|
||||
# step followed by the `if: failure()` Gitea-issue step) with the live-MXAccess run replaced by a
|
||||
# forced failure, so the issue-creation path can be exercised without burning a windev live run.
|
||||
name: tst25-check6-probe
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- 'test/tst25-check6-nightly-issue'
|
||||
|
||||
jobs:
|
||||
nightly-windev-probe:
|
||||
runs-on: ubuntu-latest
|
||||
env:
|
||||
# `github.server_url` is the runner-internal `http://gitea:3000` — correct for the API call
|
||||
# below (the job container resolves gitea only on the docker network) but useless as a link
|
||||
# a human can click. Browser-facing URLs in the issue body use the public origin instead.
|
||||
PUBLIC_SERVER_URL: https://gitea.dohertylan.com
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- name: Forced failure standing in for the live-MXAccess run
|
||||
run: exit 1
|
||||
- name: Report a red nightly as a Gitea issue
|
||||
if: failure()
|
||||
run: |
|
||||
curl -sSf -X POST \
|
||||
-H "Authorization: token ${{ github.token }}" \
|
||||
-H "Content-Type: application/json" \
|
||||
"${{ github.server_url }}/api/v1/repos/${{ github.repository }}/issues" \
|
||||
-d "{\"title\":\"[CHECK6 PROBE] nightly-windev failed on ${{ github.sha }}\",\"body\":\"The scheduled windev Worker + live-MXAccess run failed: ${PUBLIC_SERVER_URL}/${{ github.repository }}/actions/runs/${{ github.run_id }} . A red nightly may mean the Windows tier is down rather than the change — see docs/GatewayTesting.md (Continuous Integration).\"}"
|
||||
Reference in New Issue
Block a user