ci-bot
df063dcd61
doc: note Windows CI flow (trigger run 2 to verify revert wiped run 1's marker)
CI Test / hello (push) Successful in 1s
CI Test / windows-test (push) Successful in 35s
CI Test / revert-vm (push) Successful in 7s
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
...
CI Test / hello (push) Successful in 1s
CI Test / windows-test (push) Successful in 8s
CI Test / revert-vm (push) Successful in 7s
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
...
CI Test / hello (push) Successful in 1s
CI Test / windows-test (push) Successful in 7s
CI Test / revert-vm (push) Successful in 8s
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
...
CI Test / hello (push) Successful in 1s
CI Test / windows-test (push) Successful in 7s
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
CI Test / hello (push) Successful in 1s
CI Test / windows-test (push) Failing after 2m42s
2026-05-01 11:44:43 -04:00
81873ebf42
add ci workflow
CI Test / hello (push) Successful in 14s
2026-04-26 11:39:40 -04:00
b248e90441
Initial commit
2026-04-26 11:39:32 -04:00
