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.

Drop the legacy run-record import

59badc638dde0655b11d01eebfe3a457735d2501 · Keenan Nemetz · 10d ago · parent b312e166

Drop the legacy run-record import

There is no released instance to stay compatible with, so the file format
under runs/, the branch importer, and the pre-receive allowance for that
directory are gone. The Record value is now only the finish wire format and the
shape stored in run_attempts. metadata.ValidateIssues rejects runs/ like any
other unknown directory, and vole admin index rebuild no longer reads run
history from Git.

An existing instance migrates once with the previous build, then rewrites the
vole branch to remove the old records. Nothing in this build reads them.

docs/operations.md +2−11

@@ -99,12 +99,6 @@ fetched, but only a maintainer can push them; existing change requests still nam
	99	99	the same head commit. A contributor who wants to keep working pushes the same
	100	100	commit under their new folder and opens a request from it.
	101	101
	102		CI records moved from the `vole` branch to `data/runs.db`. Upgrade the server and
	103		its runners together: an older runner's finish message carries no record and is
	104		refused. Run `vole admin index rebuild` once after upgrading to import any records
	105		still on a repository's branch, and start backing up `runs.db`. A job that was
	106		running during the upgrade may need to be rerun.
	107
	108	102	Large files, CI logs, and build artifacts live in `data/lfs/`. Back that directory
	109	103	up too if you need those files. `vole admin gc` treats files reachable from a
	110	104	repository, an archived CI log, or a published artifact as things to keep.
@@ -138,11 +132,8 @@ vole admin index rebuild
	138	132	`data/runs.db` holds the CI queue, finished-run records, and contributor-branch CI
	139	133	approvals. It is a source of truth, not a rebuildable index: deleting it loses CI
	140	134	history as well as attempts that were in progress. Back it up with the rest of the
	141		instance.
	142
	143		`vole admin index rebuild` imports run records that are still on an older
	144		repository's `vole` branch. It cannot restore records written after CI history moved
	145		into the database; only a `runs.db` backup can do that.
		135	instance. `vole admin index rebuild` rebuilds only the repository and issue index;
		136	it cannot restore CI history.
	146	137
	147	138	## Security notes
	148	139