Kiln and factories-hub
Kiln is factories-hub with the changes on this page. The five skills and the state machine are the same files, at commit c941bac.
#What Kiln changes
In factories-hub | In Kiln |
|---|---|
| You copy the template, and do each setup step | kiln new does them |
| Paseo shows and starts sessions | Herdr and the Factory panel |
| GitHub Actions runs CI and the review | AWS CodeBuild |
| The hosted Flow reviewer | The flow-code-review skill and reviewdog on CodeBuild |
#What Kiln adds
scripts/factory-session.sh, which starts one session for a button of the panel.- Interface skills.
- Two session rules from the hub of AdonisJS:
working-with-the-person.mdandwriting.md.
#What Kiln does not have
The factory has a worker: scripts on a factory machine that claim tasks, watch pull requests and start sessions with no person. It needs macOS and Paseo, so Kiln leaves it out, and you press the buttons. This changes these parts of the factory:
- The builder. Nothing starts a build when a task is
ready. You press Build. - The watcher. Nothing starts
triagewhen a pull request changes. You press Triage. A merge does not startaccept. You press Accept, so the statusacceptingis not used. - Drafts. Nothing makes a pull request a draft while a task is reworked. A
triagecomment can still say that it is a draft. - The factory identity. Sessions act on GitHub as you, not as a GitHub App.
- The fleet. A fault outside a task has no fleet repository to go to.
Run builds on a machine in factories-hub explains the worker.
#Not proven yet
These parts of Kiln have not run on a real product.
kiln newbuilding the newest Flow. Each test used an earlier tarball.kiln newon real GitHub and AWS. Its tests used stand-ins forghandaws.kiln connectandkiln reviewas they are now. The steps inside them ran on real AWS in an earlier form.- CI on the
api-monorepokit, and the Flow review posting a finding in a monorepo. - An exploration, from
intaketodone. scripts/sync-issues.mjson a real repository. It passed a dry run.- macOS.