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.

Run CI jobs in a container chosen by the runner

7da9111ecabb236d48fc48592cd3d1d45f9afe78 · Keenan Nemetz · 15d ago · parent 474a812d

Run CI jobs in a container chosen by the runner

Each lease gets a disposable checkout and, when --image is set, its own container from that image. The runner keeps the SSH key and trusted Git cache outside the job, so workflow code cannot reach either; older caches are rebuilt because a previous job may have written to them.

The record names the image and runtime, and the queue mirrors them for the run page. Without --image the runner still executes on the host and says so.

docs/architecture.md +6−3

@@ -117,6 +117,9 @@ caller lives in the packages above.
	117	117	## Scope
	118	118
	119	119	Vole is built for one team on one server. It does not support multiple tenants,
	120		federation, container-isolated CI steps, custom domains with automatic
	121		certificates, horizontal scaling, or a Kubernetes deployment story. These are not
	122		part of Vole today.
		120	federation, custom domains with automatic certificates, horizontal scaling, or a
		121	Kubernetes deployment story. These are not part of Vole today.
		122
		123	CI isolation is a runner decision rather than a workflow feature: the runner can
		124	execute each job in a container from an image the operator chooses, but Vole does
		125	not pull images, choose dependencies, or orchestrate containers from the server.