On 17/02/16 11:54, Martin Lucina wrote:
Update: Looks like Docker Hub is the wrong tool for this (packages
autobuilds). So, I'll set up something on a hosted server
(Jenkins/buildbot/cronjob) and use that instead.
For the packages autobuilds, does anyone particularly need a fancy
dashboard, or are emails sent to rumprun-builds enough of an interface?
I have a request for the process of setting up the builds being
documented to the extent where someone can repeat the setup in case e.g.
if the institution footing the bill decides to not want to anymore, or
the free service chosen decides to become non-free or otherwise
difficult, or someone wants to build all packages themselves from source
for [an illusion of] security. That's not to say that it needs to be a
script that a person plucked off the street could run and be good to go,
but rather something where an aura of consistency could be retained even
if external factors are not in our favour.
In other words: repeatable experiments, for science!
Beyond that, a stable URL to "latest [official] build" would be nice,
e.g. via DNS (cf. builds.rumpkernel.org). That URL would take a lot of
guesswork out of "hey this fails for me, should it?".
At any rate, very cool.
