mhoennigandClaude Fable 5.1
bbb4969fb9
FollowUpTrigger listens to build status transitions and, on a SUCCESS, enqueues every definition of that branch whose afterSuccessOf names the finished build — at the finished build's commit, not the branch's current head, so a deployment ships the commit that was tested. Every green run triggers, a repeated one again. The trigger is armed by Watcher.start() and disarmed by stop(), so a CLI build never enqueues into a JVM about to exit; the CLI names the follow-ups the server would run instead. The event now carries the repository the result belongs to, which the listener has to act on. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Werkator
Lightweight, declarative and highly opinionated software build system (CI/CD).
Documentation
- docs/configuration.md — configuration reference
- docs/bootstrapping.md — initializing a repository with
init - docs/deployment.md — running Werkator as a systemd service behind a reverse proxy
Developer Setup
Source .envrc to add tools/ to your PATH, or install direnv to have this done automatically on cd:
source .envrc
Common tasks:
./gradlew build # compile and run all checks
./gradlew test # run tests
./gradlew ktlintFormat # auto-format Kotlin sources
./gradlew ktlintCheck # check formatting (also runs as part of build)
adr-status # show all architecture decisions at a glance
direnv
direnv sources .envrc automatically whenever you enter the repository and unloads it when you leave.
# Ubuntu
sudo apt install direnv
# add to ~/.bashrc or ~/.zshrc
eval "$(direnv hook bash)" # or: eval "$(direnv hook zsh)"
Trust the project's .envrc once per clone:
direnv allow
Tools (tools/)
| Command | Description |
|---|---|
adr-status |
List all Architecture Decision Records with their status and decision summary |
Architecture Decision Records
Major technical decisions are documented as ADRs in docs/adrs/.
adr-status # show all decisions at a glance
New ADRs follow the template at docs/adrs/0000-00-00.adr-template.md.