> > 1) Figure out a CI build pipeline for (toolchain) -> (packages). The goal > here is to periodically verify that all the packages build against a > toolchain from recent master. > > The question is where to get the toolchain for packages from -- Travis > builds can't depend on the output of other builds -- Right now I think the > best approach is that the pipeline should use one of my dockerized > toolchains (e.g. mato/rumprun-toolchain-hw-x86_64) to build packages. The > value of this approach is that any package maintainer can re-create a build > failure locally using the exact same toolchain. >
I think yes Docker is a good way to have a build environment that can be run anywhere. > 2) Building binaries, i.e. ready-to-run unikernel images where the end user > just needs to "add some data/configuration" and deploy. That's a separate > discussion, let's solve 1) first. > Sure. One requirement is I'd like those build artefacts to be easily available in the resultant Docker image so that subsequent stages (e.g. (3) publishing) can pick them up.
