Factory: acceptance runs in throw-away containers via an optional test runner service
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
63816c45fd
commit
115e9aec6c
9 files changed
+794
-11
No files matched your search
@@ -3,6 +3,16 @@
|
||||
All notable changes to CodeCraft. Versions follow [Semantic Versioning](https://semver.org/);
|
||||
until 1.0, minor versions may contain breaking changes.
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **Factory: acceptance runs in throw-away containers.** A new optional service, `testrunner` (`codecraft testrunner`, enabled with `COMPOSE_PROFILES=runner`), owns the Docker socket – the CodeCraft container does not. For every acceptance run it creates a private network, starts the app from `.factory/setup.json` in a fresh container (image, `install`, `start`, `port`, `env`; optionally built from a `dockerfile`) plus helper `services` such as a database, forwards the port to `localhost` for the agent, writes the app's log to `.factory/app.log` and removes everything afterwards. Sources are copied in, never mounted; capabilities are dropped, memory/CPU/process limits apply, and leftovers are swept at startup and after 90 minutes. Without the runner nothing changes: the agent starts the app itself.
|
||||
|
||||
### Changed
|
||||
|
||||
- Compose files: new optional `testrunner` service and `CODECRAFT_RUNNER_URL` / `RUNNER_TOKEN` in `.env.example`.
|
||||
|
||||
## [v202611-00066] – 2026-11-19
|
||||
|
||||
### Added
|
||||
|
||||
Reference in new issue
Block a user