That's a great question James. So for the past ~8 months we've been using a jenkins master + (n) slaves setup to build images. We currently build around ~20 different images for production, a few of which are also setup to separately for CI (building a GitHub pull request, tagging with a branch name, running unit/integration tests and pushing the image on success). To be honest, this actually does work pretty well. Docker is a stable bit of kit, and most of the issues we ran into were environmental... though still a problem. I think this approach is valid, and will work for most users - and even better if you couple if with the Jenkins on Mesos framework.
I'd like to highlight a few of the problems we found with running that infrastructure; - Even though we have a fair few number of images, people don't build images 24/7. However, we have some big machines up 24/7 to serve the image builds such that they complete in a timely manor when required... people don't like to wait for things, and something like this can block a developer unnecessarily. On 4 September 2014 11:06, James Gray <zaa...@gmail.com> wrote: > This is def interesting for us as this is a problem we are facing too. > > But just to clarify, what is the advantage of this approach over > submitting Docker build jobs to either the Chronos or Jenkins > schedulers? For our use case, we were thinking about writing a > scheduler for GoCD (which we use for CI/CD) to work much in the same > way as the existing Jenkins scheduler. > > On Thu, Sep 4, 2014 at 12:29 AM, Joe Smith <yasumo...@gmail.com> wrote: > > +1 to a registry, stuff like NPM, vagrantcloud, and docker make it very > > clean to search (but seems like it takes more work to support and setup). > > > > Tom- this is rad! Also loving the use of Pesos- definitely looking > forward > > to to more contributors there :) > > > > > > On Wed, Sep 3, 2014 at 4:13 PM, Chris Aniszczyk <z...@twitter.com> wrote: > >> > >> Just an idea but I think we should strive to provide a better approach > >> that is more scalable/searchable IMHO as the number of frameworks > continue > >> to grow. I created an issue here to discuss potential options and if > people > >> are interested in providing some type of framework registry: > >> https://issues.apache.org/jira/browse/MESOS-1759 > >> > >> I see a couple options that could be interested, either the more lax > >> community driven approach that JenkinsCI does via a GitHub organization > or > >> building a web-based registry similar to what the docker/ansible folks > have > >> done. > >> > >> > >> On Wed, Sep 3, 2014 at 6:03 PM, Vinod Kone <vinodk...@gmail.com> wrote: > >>> > >>> This is great Tom. Thanks for sharing. We do list Mesos frameworks on > the > >>> website ( > http://mesos.apache.org/documentation/latest/mesos-frameworks/). > >>> Please send a PR or RB request. > >>> > >>> > >>> On Wed, Sep 3, 2014 at 3:50 PM, Tom Arnfeld <t...@duedil.com> wrote: > >>>> > >>>> @Ankur Wups! That's silly of me... > >>>> http://github.com/duedil-ltd/portainer > >>>> > >>>> > >>>> On 3 September 2014 23:45, Ankur Chauhan <an...@malloc64.com> wrote: > >>>>> > >>>>> Could you share a link to the repo? > >>>>> > >>>>> > >>>>> On Wed, Sep 3, 2014 at 3:20 PM, Tom Arnfeld <t...@duedil.com> wrote: > >>>>>> > >>>>>> Hey everyone, > >>>>>> > >>>>>> Thought it would be worth sharing this on the mailing list. We've > >>>>>> recently open sourced a Mesos framework called Portainer, which is > for > >>>>>> building docker containers on top of your cluster. > >>>>>> > >>>>>> It is in working order, though very early stage... It supports all > >>>>>> Dockerfile instructions (including ADD) and can build multiple > images in > >>>>>> parallel. It's written entirely in Python, and is also built upon > the Pesos > >>>>>> python framework API @wickman, @nekto0n and I have been working on, > so > >>>>>> there's no need to install libmesos to use the framework. > >>>>>> > >>>>>> I ended up trying out the idea because we've had a painful > experience > >>>>>> managing dedicated infrastructure for building all of our images, > which I'm > >>>>>> sure some of you can empathise with, and figured we could leverage > the spare > >>>>>> capacity on our new Mesos cluster to cut that out entirely. > >>>>>> > >>>>>> We'd love any feedback or suggestions, as well as any contributions! > >>>>>> Looking forward to hearing what you all think. :-) > >>>>>> > >>>>>> Side note... It would be great if there were a place we could list > all > >>>>>> of the known frameworks for users to explore, maybe this already > exists? > >>>>>> > >>>>>> Cheers, > >>>>>> > >>>>>> Tom (and the rest of the infra team at DueDil). > >>>>>> > >>>>> > >>>> > >>> > >> > >> > >> > >> -- > >> Cheers, > >> > >> Chris Aniszczyk | Open Source | Twitter, Inc. > >> @cra | +1 512 961 6719 > > > > >
