On Thursday, 18.02.2016 at 21:36, David Halls wrote: > On 17 February 2016 at 12:26, Dejan Strbad <[email protected]> wrote: > > > Okay. Will take a look at Travis CI over the weekend and see what can be > > done. > > > > Maybe we can combine efforts. I'd like to build on a hosted CI too and > produce a set of binaries.
Lets. I'm on holiday next week, but would like to get onto this ASAP when I get back. I think there are two separate steps here: 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. 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. > I guess the .travis.yml + build scripts could be checked into > rumprun-packages? For 1) above, yes. We'd want to split the individual package builds into separate build jobs using the build matrix feature. > I was thinking of using CircleCI, you get 2 hours of build time. But Travis > works well too. 2 hours should work for everything except the rust toolchain :-)
