ci-test

9 commits 1 branch 0 tags 34 KiB

Author	SHA1	Message	Date
ci	5e98ea25fd	ci: retrigger after attaching runner jobs to web network All checks were successful CI Test / hello (push) Successful in 1s Details CI Test / windows-test (push) Successful in 18s Details CI Test / revert-vm (push) Successful in 6s Details	2026-05-02 06:34:25 -04:00
ci	1423c7c11c	ci(windows): scp tests/ into VM and run PowerShell test suite Some checks failed CI Test / hello (push) Successful in 1s Details CI Test / windows-test (push) Failing after 41s Details CI Test / revert-vm (push) Successful in 8s Details	2026-05-02 06:31:40 -04:00
ci-bot	df063dcd61	doc: note Windows CI flow (trigger run 2 to verify revert wiped run 1's marker) All checks were successful CI Test / hello (push) Successful in 1s Details CI Test / windows-test (push) Successful in 35s Details CI Test / revert-vm (push) Successful in 7s Details	2026-05-01 14:43:41 -04:00
ci-bot	db0f36e029	ci(windows): drop a marker file each run and assert it's gone next run All checks were successful CI Test / hello (push) Successful in 1s Details CI Test / windows-test (push) Successful in 8s Details CI Test / revert-vm (push) Successful in 7s Details If two runs in a row both pass, the revert flow is provably wiping state between runs. If the second one fails on 'Verify clean baseline', the revert isn't doing its job.	2026-05-01 14:42:56 -04:00
ci-bot	c1bd0ec9f9	ci(windows): add always-runs revert job that rolls the VM back to gold All checks were successful CI Test / hello (push) Successful in 1s Details CI Test / windows-test (push) Successful in 7s Details CI Test / revert-vm (push) Successful in 8s Details Calls the host's testing-revert HTTP endpoint after windows-test (whether it passed or failed), so every CI run starts from the gold snapshot.	2026-05-01 14:37:49 -04:00
ci-bot	71b7db4985	ci(windows): resolve host gateway at runtime instead of hardcoding 172.17.0.1 All checks were successful CI Test / hello (push) Successful in 1s Details CI Test / windows-test (push) Successful in 7s Details Forgejo Runner spawns each job on a per-job custom Docker network whose gateway is not the default bridge (172.17.0.1). Detecting the default route inside the container picks up whatever bridge gateway is in use.	2026-05-01 14:32:47 -04:00
ci-bot	202798219d	ci: add windows-test job that runs commands inside the testing VM via SSH Some checks failed CI Test / hello (push) Successful in 1s Details CI Test / windows-test (push) Failing after 2m42s Details	2026-05-01 11:44:43 -04:00
forgejoadmin	81873ebf42	add ci workflow All checks were successful CI Test / hello (push) Successful in 14s Details	2026-04-26 11:39:40 -04:00
forgejoadmin	b248e90441	Initial commit	2026-04-26 11:39:32 -04:00