ci: run the forge tests on the harness in the gate and in CI, and remove the docker-exec smoke job #678

New issue

Open

opened 2026-09-29 23:05:15 +00:00 by hexajon · 0 comments

hexajon commented

2026-09-29 23:05:15 +00:00

Owner

What to build

The gate and the CI gate job run the forge tests against both forges. No forge test is skipped.
The commands in tests/integration/forgejo-smoke.sh move onto the harness as Go tests, and run against both forges.
The forgejo-smoke job in .forgejo/workflows/drift.yml goes, with its docker exec bootstrap and the RUN_FORGEJO_SMOKE variable.

Acceptance

The gate output and the CI gate log each show that the forge tests ran against Forgejo and against Gitea, with no skipped forge test.
drift.yml has no docker exec and no RUN_FORGEJO_SMOKE.

Needs #677. Part of #674.

## What to build - The gate and the CI `gate` job run the forge tests against both forges. No forge test is skipped. - The commands in `tests/integration/forgejo-smoke.sh` move onto the harness as Go tests, and run against both forges. - The `forgejo-smoke` job in `.forgejo/workflows/drift.yml` goes, with its `docker exec` bootstrap and the `RUN_FORGEJO_SMOKE` variable. ## Acceptance - The gate output and the CI `gate` log each show that the forge tests ran against Forgejo and against Gitea, with no skipped forge test. - `drift.yml` has no `docker exec` and no `RUN_FORGEJO_SMOKE`. Needs #677. Part of #674.

hexajon referenced this issue

2026-09-29 23:06:02 +00:00

epic: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy #674

hexajon added a new dependency

2026-09-29 23:06:10 +00:00

#674 epic: run forge tests against throwaway Forgejo and Gitea servers behind a real proxy

hexajon added a new dependency

2026-09-29 23:06:10 +00:00

#677 tests: add a harness that starts throwaway Forgejo and Gitea servers behind Traefik

hexajon referenced this issue

2026-10-03 16:55:44 +00:00

gate: run the forge tests only inside an Incus VM #692