Test repositories from experiment runs get a cleanup rule and a script
Each experiment run of Satsuma's autonomous system creates its own private code repositories for the products it builds. A session in the system took stock of them: seven repositories, created by the first three runs, all test artefacts. "None of these are production." Every run starts two fresh local chains, so the contracts those repositories describe no longer exist anywhere.
A cleanup script landed. It deletes a run's repositories by their name suffix and does a dry run first. The dry run confirmed the same seven targets.
The rule is now written down: per-run repositories are test artefacts, deleted by hand once the run is archived, and the archive is the record. A fourth run is still building, and its repositories follow the same route once it is archived.
The seven have not been deleted. An automated safeguard blocked the deletion as irreversible, so the commands were handed to the operator to run by hand.
- Harness: delete a run's product repos once it is archived (by hand; the archive is the record)The system
- Deleting the seven repositories directly from the session; an automated safeguard blocked it as irreversible
- Per-run repositories are test artefacts, deleted by hand after each run is archived; the archive is the record
- The fourth run's repositories follow the same cleanup route once it is archived
- The seven repositories from the first three runs still have to be deleted by hand
- The fourth run is still building; its repositories are not yet created or cleaned up