The Custom Build panel in Bluespeed is the contributor's OS image factory: define a recipe or Containerfile, trigger a build, watch it run, the output image is ready to push to the fleet. The reference implementation ships with 2 options BlueBuild since it exists and is mature and would be perfect for this! The 2nd major setup is the user's own buildstream setup, which will be what we'd want long term but someone needs to build it. Or bluebuild get's bst support. That'd work!
This is the Chromebook vision — every contributor has their own cloud-native OS factory on their own hardware.
What it shows:
- My Images: list of built OCI images in Zot, latest digest, build time, push-to-fleet action
- Build History: recent Argo Workflows runs with status, duration, link out to Argo Workflows UI for full logs
- New Build trigger
- Prominent link to the contributor's BlueBuild URL
Supported paths (all first-class):
| Input |
Base |
Notes |
| BuildStream |
From source |
Implement first |
| recipe.yml (BlueBuild) |
Fedora bootc |
Default example shipped with bluespeed |
| Containerfile |
Fedora bootc or CentOS Stream 10 |
Full control |
CNCF context: Argo Workflows (graduated) runs builds. Zot (sandbox) stores images. Argo Workflows UI is the full log surface — link out, don't rebuild it. Image list queries the Zot OCI catalog API. Keep everything on the golden path.
Principle: This panel shows status and triggers — it does not replace the Argo Workflows UI. Keep it simple. The contributor should feel proud of their images.
Relates to: #31 (OS image factory — the pipeline this panel surfaces), #34 (recipe source location)
The Custom Build panel in Bluespeed is the contributor's OS image factory: define a recipe or Containerfile, trigger a build, watch it run, the output image is ready to push to the fleet. The reference implementation ships with 2 options BlueBuild since it exists and is mature and would be perfect for this! The 2nd major setup is the user's own buildstream setup, which will be what we'd want long term but someone needs to build it. Or bluebuild get's bst support. That'd work!
This is the Chromebook vision — every contributor has their own cloud-native OS factory on their own hardware.
What it shows:
Supported paths (all first-class):
CNCF context: Argo Workflows (graduated) runs builds. Zot (sandbox) stores images. Argo Workflows UI is the full log surface — link out, don't rebuild it. Image list queries the Zot OCI catalog API. Keep everything on the golden path.
Principle: This panel shows status and triggers — it does not replace the Argo Workflows UI. Keep it simple. The contributor should feel proud of their images.
Relates to: #31 (OS image factory — the pipeline this panel surfaces), #34 (recipe source location)