DevOps Templates
Plug-and-play CI/CD pipelines for embedded and cloud projects.
Embedded projects tend to get the CI/CD they can be bothered to build, which is usually a script on one engineer’s machine. The cost shows up later, when a release cannot be reproduced or a regression is found by a customer rather than a pipeline.
These templates are the pipelines we put on our own embedded work: a build that runs in a container so it is identical everywhere, hardware-in-the-loop test stages that run on real boards, artefact handling that keeps every image traceable to a commit, and Terraform modules for the cloud side. They are meant to be adopted in an afternoon and then modified, not treated as a platform.
Embedded CI workflow
GitHub Actions that build, test and archive firmware on every push.
Cross-compilation image
A Docker toolchain so every build is the same build.
Hardware-in-the-loop
Test stages that run against real boards, not only emulators.
Terraform modules
Infrastructure described once and applied per environment.
Artefact traceability
Every image traceable to the commit and toolchain that produced it.
Release automation
Versioning, changelog and signed artefacts without manual steps.
Adopt the workflow
Drop the template in and point it at your repository layout.
Containerise the build
The toolchain moves into an image, and local builds match CI.
Add the hardware
A runner with a board attached turns tests into evidence.
Release
Tagged, signed, archived and reproducible months later.
Industrial IoT
Teams shipping firmware to a fleet who need every release accounted for.
Defense & Aerospace
Programmes with reproducibility and audit requirements on the build itself.
Medical & HealthTech
Device software where the pipeline output is part of the submission.
