vole

Clone

Read only, no credentials:

https://rodent.software/git/vole.git

Write over SSH with a registered key:

git clone ssh://git@0.0.0.0:2222/vole.git

A free and open-source forge that lives in your Git repo.

Explain attempts and reruns where the queue is described

1d06b008c5e41b4540c0f92569a5b8ac8290a814 · Keenan Nemetz · 5d ago · parent 5d7417fe

@@ -533,8 +533,16 @@ instance (`pages_ref`), not by the workflow.
	533	533	Pushing again cancels queued runs for the commit it replaced. It never stops a run
	534	534	that is already in progress; a maintainer can stop that one from its page or with
	535	535	`vole run cancel <id>`, and the runner stops at its next heartbeat. The attempt that
	536		comes back is kept as canceled. Finished runs are stored in `data/runs.db`, not on the
	537		repository's `vole` branch.
		536	comes back is kept as canceled.
	538	537
		538	A run can have more than one attempt. Each time a runner starts the job it records a
		539	new attempt, and a runner that disappears hands the job back for another one. After
		540	five attempts the run fails instead of cycling. A finished run can be queued again
		541	with Rerun on its page or `vole run rerun <id>`; that is another attempt of the
		542	same pinned workflow, image, and secrets, not a new run. A queued or running run
		543	cannot be rerun. The run page lists each attempt's log, and the log URL takes
		544	`?attempt=N`.
		545
		546	Finished runs are stored in `data/runs.db`, not on the repository's `vole` branch.
	539	547	For what happens when a runner disappears, how work is requeued, and how finished
	540	548	history is rebuilt, see [Runners § Scheduling and the queue](runner.md#scheduling-and-the-queue).