On Monday, 01.02.2016 at 17:41, Antti Kantee wrote: > Is there any progress with the automated package builds? Either they are > not running anymore, or all packages always build (if so, cool ;)
They are running, but in a semi-broken way, and I'm not getting notifications properly. I'll try and look into it this week(ish). > I still think it would be best if a build kicked off once every $timeunit > (24h?) and always sent a summary including a link to a full log (which is > viewable without any silly accounts). That would take the guesswork out of > if packages are failing or the CI system is failing. In case that scheme > proves impossible to achieve with the Docker infrastructure, maybe someone > has ideas on a better suited service. Even just using a simple custom AWS > instance (or equivalent) shouldn't be bankruptatory with the CPU cycles we > currently need to build all packages. Thoughts and/or volunteers? Kicking off a build every 24hrs should not be a problem, what is more problematic is the strict "one repo : one build : one image" Docker Hub view of the world. I've been trying to figure out a suitable way to split the single packages build into a set of per-package builds, but don't have anything working yet, sorry :-(
