A few nights ago, Ikey and ermo deployed the first publicly accessible pre-alpha version of the Serpent OS infrastructure and proved that:
- We can now pair and hook up remote builders to Summit via our Avalanche builder middleware
- Summit (our dashboard and build controller) can go from detecting and fetching new/updated stone.yml recipes from our GH repos, to issuing build jobs to our Avalanche builders, to receiving completed builds w/build status
- Summit can instruct our repository manager Vessel to fetch assets from the relevant Avalanche builder, with Vessel re-indexing the official Serpent OS
volatile moss repository on completion
- Summit can show the progress of build queues
To us, this is at once the culmination of what feels like a very long iterative design and development process and at the same time, the fresh, first step in the exciting process of development and refinement of our tooling and the workflows it supports for the packaging lifecycle in Serpent OS.
Our contributors (you know who you are!) have also been prolific in contributing not only code and package recipe PRs with bug fixes and new features, but have also been actively involved with design and workflow suggestions and have shown great initiative in fleshing out useful ideas for improving not only packages but indeed tooling and even deployment scenarios.
We will of course continue to work on extending and improving the infrastructure and the processes surrounding it. Onwards and Upwards! 🚀