introducing spindle
Since launching Tangled, continuous integration has consistently topped our feature request list. Today, CI is no longer a wishlist item, but a fully-featured reality.
Meet spindle: Tangled’s new CI runner built atop Nix and AT Protocol. In typical Tangled fashion we’ve been dogfooding spindle for a while now; this very blog post you’re reading was built and published using spindle.
Spindle is designed around simplicity and the decentralized nature of the AT Protocol. In ingests “pipeline” records and emits job status updates.
When you push code or open a pull request, the knot hosting your repository emits a pipeline event (sh.tangled.pipeline). Running as a dedicated service, spindle subscribes to these events via websocket connections to your knot.
Once triggered, spindle reads your pipeline manifest, spins up the necessary execution environment (covered below), and runs your defined workflow steps. Throughout execution, it streams real-time logs and status updates (sh.tangled.pipeline.status) back through websockets, which the Tangled appview subscribes to for live updates.
