CI workflow never succeeds — all 32 workflow runs are failure/cancelled, no build artifact produced #20

New issue

Closed

opened 2026-08-11 02:56:34 +00:00 by Mark · 1 comment

Mark commented

2026-08-11 02:56:34 +00:00

Owner

Finding

The .forgejo/workflows/ci.yml build workflow for this repo has never succeeded: all 32 workflow runs are failure or cancelled. No JAR artifact has ever been produced or uploaded by CI, which directly blocks every downstream deploy (see issue about #4 fix never shipping).

Source: kanban qa card t_e91b153c (probe findings, 2026-08-10).

Repro steps

GET /repos/Mark/mc-heroes-mod/actions/runs?limit=25 — list all runs.
Observe status: 29 failure + 3 cancelled (ids 1569..5368), zero success.
Check the workflow (.forgejo/workflows/ci.yml): it sets up JDK 21 (temurin), runs ./gradlew build --no-daemon --stacktrace in project/, then uploads project/build/libs/*.jar.
Confirm no run ever reaches the artifact upload (no success status, no artifacts).

Actual vs expected

Expected: every push runs the workflow; on success a mod-jar artifact is uploaded.
Actual: all runs fail or are cancelled; the workflow never produces a build artifact. Issue #16 ("CI: Gradle build fails — JDK not available in runner container") was closed 2026-05-14 but CI is still failing on every run since.

Impact

Without a successful CI build there is no artifact to install anywhere; this is the root cause of "fix #4 never deployed". Needs workflow/runner diagnosis (runner label, JDK provisioning, Gradle build errors).

Kanban card: t_e91b153c (this card)
Fixit card: t_a4d2d489
Issue #16: prior CI JDK failure (closed 2026-05-14, did not resolve)
Issue #4: closed 2026-08-05, fix never built/deployed

## Finding The `.forgejo/workflows/ci.yml` build workflow for this repo has **never succeeded**: all 32 workflow runs are `failure` or `cancelled`. No JAR artifact has ever been produced or uploaded by CI, which directly blocks every downstream deploy (see issue about #4 fix never shipping). Source: kanban qa card `t_e91b153c` (probe findings, 2026-08-10). ## Repro steps 1. `GET /repos/Mark/mc-heroes-mod/actions/runs?limit=25` — list all runs. 2. Observe status: 29 `failure` + 3 `cancelled` (ids 1569..5368), **zero** `success`. 3. Check the workflow (`.forgejo/workflows/ci.yml`): it sets up JDK 21 (temurin), runs `./gradlew build --no-daemon --stacktrace` in `project/`, then uploads `project/build/libs/*.jar`. 4. Confirm no run ever reaches the artifact upload (no success status, no artifacts). ## Actual vs expected - **Expected:** every push runs the workflow; on success a `mod-jar` artifact is uploaded. - **Actual:** all runs fail or are cancelled; the workflow never produces a build artifact. Issue #16 ("CI: Gradle build fails — JDK not available in runner container") was closed 2026-05-14 but CI is still failing on every run since. ## Impact Without a successful CI build there is no artifact to install anywhere; this is the root cause of "fix #4 never deployed". Needs workflow/runner diagnosis (runner label, JDK provisioning, Gradle build errors). ## Related - Kanban card: `t_e91b153c` (this card) - Fixit card: `t_a4d2d489` - Issue #16: prior CI JDK failure (closed 2026-05-14, did not resolve) - Issue #4: closed 2026-08-05, fix never built/deployed

Mark added the

bug

label

2026-08-11 02:56:34 +00:00

Mark referenced this issue from a commit

2026-08-11 10:25:17 +00:00

fix #19, #20: CI workflow never succeeds — route to healthy runner, use Forgejo action mirror

Mark referenced this issue from a commit

2026-08-11 11:21:22 +00:00

fix #20: upload-artifact v4 not supported on Forgejo — pin v3 (verified mirror SHA)

Mark closed this issue

2026-08-11 11:21:22 +00:00

Mark commented

2026-08-11 11:28:45 +00:00

Author

Owner

Fixed in bc96704 (pushed to main). The build pipeline now runs end-to-end and succeeds — run #5519: checkout ✓, setup-java ✓, ./gradlew build ✓ (BUILD SUCCESSFUL in 2m51s, 16/16 tests), upload-artifact ✓, mod-jar artifact attached.

Three stacked bugs:

No runner registered for this repo → every run stuck waiting (registered localhost-mcheroes-runner via repo registration token).
Action refs https://github.com/actions/*.git@v4 never resolved → switched to data.forgejo.org mirror with verified SHA pins.
upload-artifact@v4 fails on Forgejo with GHESNotSupportedError → pinned v3 (verified mirror SHA ff15f030, v3.2.1).

Verification: git log origin/main shows 9b11198 + bc96704; run #5519 status=success with artifact. Closing.

Fixed in bc96704 (pushed to main). The build pipeline now runs end-to-end and succeeds — run #5519: checkout ✓, setup-java ✓, `./gradlew build` ✓ (BUILD SUCCESSFUL in 2m51s, 16/16 tests), upload-artifact ✓, `mod-jar` artifact attached. Three stacked bugs: 1. No runner registered for this repo → every run stuck `waiting` (registered localhost-mcheroes-runner via repo registration token). 2. Action refs `https://github.com/actions/*.git@v4` never resolved → switched to data.forgejo.org mirror with verified SHA pins. 3. `upload-artifact@v4` fails on Forgejo with GHESNotSupportedError → pinned v3 (verified mirror SHA ff15f030, v3.2.1). Verification: `git log origin/main` shows 9b11198 + bc96704; run #5519 status=success with artifact. Closing.