Also, there's a tool called mesosctl (https://github.com/mesoshq/mesosctl) if you want to start small.
338 karma · joined April 30, 2015
I love the lightweight approach with GitLab CI, it's really easy to get started with. I currently don't miss any significant functionality, but I guess our builds are not that complex.
As we're running our complete infrastructure on Mesos/Marathon, I wonder whether it'd be possible to use the new autoscaling for the runners with Marathon instead of docker-machine. Basically, the only thing I'd need to be able to is to retrieve the registration token for the runners via a API, so that it can be passed in when the new Docker container(s) is/are spun up.
Currently (we're still using the old runner version in a custom Docker image, https://hub.docker.com/r/tobilg/gitlab-runner/), we scale them manually via Marathon.
Probably it's easy to integrate Mesos/Marathon additionally to docker-machine, because the mechanism for scaling seem to be the same.
I think this will be beneficial to Mesos users, bescause it will be very easy to use and scale GitLab on it.
The Graph API has not longer the ability to retrieve the /home endpoint which contained the newsfeed, since v2.0. The only this a app can retrieve is the user's own posts.
Even within the Mesos environment, there are so many nuts and bolts which have to fit together that sometimes I'm just fed up with the complexity. Furthermore, releases of Mesos and Marathon are not necessarily synched... Stateful apps? No go... Persistent volumes in Marathon? Maybe in v0.16... Graceful shutdown of Docker containers? No go...