Hi all, as those of you subscribed to the [email protected] list may have already noticed, I've set up automated builds for the rumprun-packages repository using Docker Hub.
These builds are intended to serve as CI for the rumprun-packages repository; builds are automatically started whenever new commits are pushed to either rumpkernel/rumprun-packages or rumpkernel/rumprun[1]. Due to limitations on the Docker Hub side, currently only notifications about automated build *failures* are sent to rumpkernel-builds. Each notification contains an URL of the corresponding build that failed, you can view the build logs on that page[2]. I've started raising issues against the relevant packages which don't build, if you want to reproduce the exact same build environment it is generally quicker when iterating to build the docker images yourself on a local machine with docker installed rather than waiting for the Docker Hub build cycle to complete. To do that, clone the source repository, https://github.com/mato/rumprun-docker-builds, edit the appropriate Dockerfile to enable only the packages you are interested in and run e.g. "docker build -t testing packages-hw-x86_64/". Enjoy, Martin [1] To be precise, the rumprun-packages-* images are linked to the toolchain images as described here: http://wiki.rumpkernel.org/Howto%3A-Using-prebuilt-Rumprun-toolchains-with-Docker. Due to some issues with the Github->Docker webhook chain you may see more than one build triggered per commit to rumpkernel/rumprun-packages. [2] To view the build logs you currently must have a Docker Hub account and be logged in. See https://github.com/docker/hub-feedback/issues/438
