> The 'inheritance' heirarchy is: > > ubuntu > davedoesdev/rumprun-toolchain-base > davedoesdev/rumprun-toolchain-base-hw > davedoesdev/rumprun-toolchain-x86_64-rumprun-netbsd-hw
I got fed up with installing the package deps on Travis so I made another image, davedoesdev/rumprun-pkgbuild-x86_64-rumprun-netbsd-hw, which sits at the bottom of the heirarchy: ubuntu davedoesdev/rumprun-toolchain-base davedoesdev/rumprun-toolchain-base-hw davedoesdev/rumprun-toolchain-x86_64-rumprun-netbsd-hw davedoesdev/rumprun-pkgbuild-x86_64-rumprun-netbsd-hw It basically adds dependencies required by the packages to the Docker image, which means each build in the matrix doesn't have to repeat the installations. Regarding publishing the package build artifacts, I'm doing that in the 'publish' branch of https://github.com/davedoesdev/rumprun-packages. I'm planning to do something similar to Alpine Linux, which builds on a public CI (Circle CI in their case) and pushes from there: https://github.com/gliderlabs/docker-alpine/blob/master/build#L70 They set their Docker credentials separately using Circle CI's Web interface so they're not publicly visible: https://github.com/gliderlabs/docker-alpine/blob/master/build#L70 I intend to do something similar, but on Travis CI and using dtuf so you won't need Docker to run them. Again, and comments/opinions/advice/don't-do-that-it's-stupid accepted. David
